Details
-
Bug
-
Resolution: Answered
-
Medium
-
None
-
3.1, 3.2
-
None
-
None
Description
It is probably too late now to change, but buildKey variable should NOT have been changed! It now results is a job key instead according to http://confluence.atlassian.com/display/BAMBOO/Using+Global,+Plan+or+Build-specific+Variables. A new variable should have been added like jobKey or similar. At a minimum, a new variable should be available to get back to the former buildKey.
Looks like docs changed in 3.1, not sure when the code actually changed.
This impacted our bamboo automation after upgrade to 3.2 - although it was fairly minor. Except now we need the old plan key.