We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-14891

Deployment -- branch deployment ignores Release Version rules

    • 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
          1.jpg
          93 kB
        2. 2.jpg
          2.jpg
          105 kB
        3. 3.jpg
          3.jpg
          27 kB
        4. 4.jpg
          4.jpg
          90 kB
        5. 5.jpg
          5.jpg
          74 kB
        6. 6.jpg
          6.jpg
          86 kB
        7. 7.jpg
          7.jpg
          55 kB
        8. 7.jpg
          7.jpg
          56 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bamboo Data Center'
            1. Bamboo Data Center
            2. BAM-14891

            Deployment -- branch deployment ignores Release Version rules

              • 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
                    1.jpg
                    93 kB
                  2. 2.jpg
                    2.jpg
                    105 kB
                  3. 3.jpg
                    3.jpg
                    27 kB
                  4. 4.jpg
                    4.jpg
                    90 kB
                  5. 5.jpg
                    5.jpg
                    74 kB
                  6. 6.jpg
                    6.jpg
                    86 kB
                  7. 7.jpg
                    7.jpg
                    55 kB
                  8. 7.jpg
                    7.jpg
                    56 kB

                        mgardias Marcin Gardias
                        13a993b96b56 Andrew Bilukha
                        Votes:
                        34 Vote for this issue
                        Watchers:
                        30 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

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

                              Created:
                              Updated:
                              Resolved: