Closed sohrab- closed 7 years ago
The work-around I am currently looking at is to use the exposed Bamboo API, deploymentProjectService.updateVersionNamingScheme()
, directly.
However I am having trouble stopping Bamboo from evaluating ${bamboo.buildNumber}
too early, even when changing it to bamboo_buildNumber
. How do you do it in the plugin where it doesn't substitute it too early?
Fixed with release 1.9.3. Thanks for reporting it!
Bamboo 6.1 provides the feature where the branch plan inherits the release versioning of the main plan.
Currently we cannot toggle this in the DSL.
Also even if I set them manually, next run of the Seed Plan clears the option.