Steps to reproduce:
1) create plan, script task:
echo $bamboo_buildResultKey echo $bamboo_buildNumber
2) run the plan
3a) expected result (in the logs) is to see something like
PROJ-PLAN-JOB1-1 1
3b) while current behavior is:
(these environment variables are undefined, that's why we see empty logs)
Seems we pass the plan/global variables into the environment:
But we don't do that for built-in variables like:
- ${bamboo.buildPlanName}
- ${bamboo.buildKey}
- ${bamboo.buildNumber}
- ${bamboo.buildResultKey}
- ${bamboo.buildTimeStamp}
- ${bamboo.repository.revision.number}
- ${bamboo.build.working.directory}
etc...
[BAM-11824] Pass the build-specific variables automatically into environment variables (like plan/global variables do)
| Workflow | Original: JAC Suggestion Workflow [ 3017797 ] | New: JAC Suggestion Workflow 3 [ 3602996 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2698821 ] | New: JAC Suggestion Workflow [ 3017797 ] |
| Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1409964 ] | New: Confluence Workflow - Public Facing v4 [ 2698821 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 606410 ] | New: Bamboo Workflow 2016 v1 [ 1409964 ] |
Plan level variables still do not appear to work in script tasks (when powershell script is enabled). I am trying to pass a plan level variable to my powershell script and cannot get it to work. Global variables work fine but plan level do not. Please advise.
We are using version 5.7.2 and I have the following script with run as powershell marked:
echo "Variables"
echo $bamboo_buildNumber
echo $bamboo_build_mode
The output is simply:
Variables
So it appears the issue still is happening for global and plan variables at least in 5.7.2