-
Bug
-
Resolution: Fixed
-
Low
-
5.5.1, 5.7.2, 5.6.2, 5.12.3.1
-
None
-
Severity 3 - Minor
-
Scenario Description:
1. We set up a custom variable AQRVersion (1.jpg) on the plan level which is used in conjunction with ${bamboo.buildNumber} for generating a Microsoft-style software version, $(bamboo.AQRVersion}.${bamboo.buildNumber} for passing it to the Deployment project. (2.jpg)
2. For the master(trunk) build it works just fine - the release version equals to the software version (3.jpg)
Something completely unexpected happens for branch builds (the idea is, of course to have a continuous deployments within the same project).
1. In GitHub we create a release branch "Release1.1", and Bamboo does a great job detecting it and setting up a branch build plan. In this branch, we override the AQRVersion with the new minor release bump (4.jpg)
2. The deployment project's Release Version rules remain unchanged, and are $(bamboo.AQRVersion}.${bamboo.buildNumber} (2.jpg)
3. We switch the deployment project to release from branch. (5.jpg)
4. BUG: Bamboo completely ignores the Release Version rule set up in Deployment Project, and proceeds to use "{Branch Name}, INJECTS A DASH, and then adds ${bamboo.buildNumber}" (6.jpg, 7.jpg).
Please fix it to be consistent, and not to ignore the Release Version rules when releasing automatic branches.
- duplicates
-
-
- Closed
-
-
BAM-14422 How to change default (from bamboo deployments) of "Releases from branches will default to using the branch name suffixed with the build number of the build result"
- Closed
- is duplicated by
-
- Closed
- was cloned as
-
BDEV-6052 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-14891] Deployment -- branch deployment ignores Release Version rules
In the upcoming Bamboo 6.1 there's going to be an option to apply the same naming scheme to all the branches
Andrew Bilukha
added a comment - Oh, wait, that's a three-year interest commitment for me... Andrew Bilukha
added a comment - Me too: Here's my one-year-later renewed interest in having this fixed – PLEASE FIX IT!
Andrew Bilukha
added a comment - Me too: Here's my one-year-later renewed interest in having this fixed – PLEASE FIX IT! Here's my one-year-later renewed interest in having this fixed – PLEASE FIX IT!
Please fix this, to have a consistent versioning across the same deployment project.
Andrew Bilukha
added a comment - Please fix this, it's a trivial update to the code. 
Ron Chan
added a comment - Not a new issue https://jira.atlassian.com/browse/BAM-14886 Also experiencing this issue, only able to access the version from the primary branch, the rest get assigned <branchname>-<buildnum>
David Weiner
added a comment - We to have seen this issue and we also think the release number should be consistent across all branches, just not the main/default branch
David Weiner
added a comment - We to have seen this issue and we also think the release number should be consistent across all branches, just not the main/default branch I'm also running into this, but on the "Create release" dialog.
When selecting a branch other than master it decides on its own that it should use <branch-name>-<buildNumber> as the release name.
The workaround in this case is to just input the versioning rule
as the name.
Bamboo 6.7.1 is still affected