-
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
-
BAM-14063 Branch deployment doesn't follow release versioning
- 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
-
BAM-15544 release scheme for branch level deployment project
- Closed
- was cloned as
-
BDEV-6052 Loading...
Deployment -- branch deployment ignores Release Version rules
-
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
-
BAM-14063 Branch deployment doesn't follow release versioning
- 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
-
BAM-15544 release scheme for branch level deployment project
- Closed
- was cloned as
-
BDEV-6052 Loading...