Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.6.0
-
None
-
Severity 3 - Minor
-
Description
This is the description from the "variables" tab:
For task configuration fields, use the syntax ${bamboo.myvariablename}. For inline scripts, variables are exposed as shell environment variables which can be accessed using the syntax $BAMBOO_MY_VARIABLE_NAME (Linux/Mac OS X) or %BAMBOO_MY_VARIABLE_NAME% (Windows).
It gives the impression that variables will be exposed in the environment with the key uppercased and dots replaced with underscores. Through trial and error, I've found that the underscore replacement happens, but the key is lowercase.
See screenshot - the variable test.foo can only be accessed via $bamboo_test_foo, not $BAMBOO_TEST_FOO as the description implies.
This is really annoying if it causes a step to fail late in a build.