Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-14891

Deployment -- branch deployment ignores Release Version rules

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 6.1.0
    • 5.5.1, 5.7.2, 5.6.2, 5.12.3.1
    • Deployments
    • None 

      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.

        1. 1.jpg
          93 kB
          Andrew Bilukha
        2. 2.jpg
          105 kB
          Andrew Bilukha
        3. 3.jpg
          27 kB
          Andrew Bilukha
        4. 4.jpg
          90 kB
          Andrew Bilukha
        5. 5.jpg
          74 kB
          Andrew Bilukha
        6. 6.jpg
          86 kB
          Andrew Bilukha
        7. 7.jpg
          56 kB
          Andrew Bilukha
        8. 7.jpg
          55 kB
          Andrew Bilukha

            [BAM-14891] Deployment -- branch deployment ignores Release Version rules

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1438577 ] New: JAC Bug Workflow v3 [ 3386247 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Tomasz Belina added a comment -

            Bamboo 6.7.1 is still affected

            Tomasz Belina added a comment - Bamboo 6.7.1 is still affected
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Marcin Gardias made changes -
            Fix Version/s New: 6.1.0 [ 71390 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Marcin Gardias added a comment -

            In the upcoming Bamboo 6.1 there's going to be an option to apply the same naming scheme to all the branches

            Marcin Gardias added a comment - In the upcoming Bamboo 6.1 there's going to be an option to apply the same naming scheme to all the branches
            Marcin Gardias made changes -
            Remote Link New: This issue links to "+core+ Bamboo Databases Tests › C DB Upgrades › BAM-14891-branch-version-naming (tardigrade-bamboo)" [ 288594 ]
            Bugfix Automation Bot made changes -
            UIS Original: 1
            Bugfix Automation Bot made changes -
            UIS New: 1
            Confluence Escalation Bot (Inactive) made changes -
            UIS Original: 2
            Marcin Gardias made changes -
            Remote Link New: This issue links to "+core+ Bamboo › C Licence › BAM-14891-branch-version-naming (tardigrade-bamboo)" [ 277346 ]

              mgardias Marcin Gardias
              13a993b96b56 Andrew Bilukha
              Affected customers:
              34 This affects my team
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: