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

Custom plan variables do not seem to resolve to their values consistently when generating a release

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 5.1
    • 5.0, 5.0.1
    • Deployments

      I have plan variables to store the major and minor versions separately, as our deploy scripts handle major and minor upgrades differently, and the variables only seem to resolve to their value half of the time when generating a new release. Funny thing is, the variables always seem to work right when I click preview on the Release Versioning page.

      To reproduce, add a variable to plan, say build.foobar = works, run the plan and then attempt to make a release out of it using the variable ${bamboo.build.foobar} in the release name. It will work in the preview, but it will frequently not work when generating the release. As far as I can tell there is nothing different happening when it works vs. when it doesn't.

            [BAM-13549] Custom plan variables do not seem to resolve to their values consistently when generating a release

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1434143 ] New: JAC Bug Workflow v3 [ 3379122 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1407938 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1434143 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 607001 ] New: Bamboo Workflow 2016 v1 [ 1407938 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 594713 ] New: Bamboo Workflow 2014 v2 [ 607001 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 548486 ] New: Bamboo Workflow 2014 [ 594713 ]
            Marcin Gardias made changes -
            Fix Version/s New: 5.1 [ 32705 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            James Dumay made changes -
            Link New: This issue relates to BAM-13556 [ BAM-13556 ]
            Sean O'Connor made changes -
            Description Original: I have plan variables to store the major and minor versions separately, as our deploy scripts handle major and minor upgrades differently, and the variables only seem to resolve to their value half of the time when generating a new release. Funny thing is, the variables always seem to work right when I click preview on the Release Versioning page.

            To reproduce, add a variable to plan, say build.foobar = works, run the plan and then attempt to make a release out of it using the using the variable $\{bamboo.build.foobar\} in the release name. It will work in the preview, but it will frequently not work when generating the release. As far as I can tell there is nothing different happening when it works vs. when it doesn't.
            New: I have plan variables to store the major and minor versions separately, as our deploy scripts handle major and minor upgrades differently, and the variables only seem to resolve to their value half of the time when generating a new release. Funny thing is, the variables always seem to work right when I click preview on the Release Versioning page.

            To reproduce, add a variable to plan, say build.foobar = works, run the plan and then attempt to make a release out of it using the variable $\{bamboo.build.foobar\} in the release name. It will work in the preview, but it will frequently not work when generating the release. As far as I can tell there is nothing different happening when it works vs. when it doesn't.
            James Dumay made changes -
            Description Original: I have plan variables to store the major and minor versions separately, as our deploy scripts handle major and minor upgrades differently, and the variables only seem to resolve to their value half of the time when generating a new release. Funny thing is, the variables always seem to work right when I click preview on the Release Versioning page.

            To reproduce, add a variable to plan, say build.foobar = works, run the plan and then attempt to make a release out of it using the using the variable ${bamboo.build.foobar} in the release name. It will work in the preview, but it will frequently not work when generating the release. As far as I can tell there is nothing different happening when it works vs. when it doesn't.
            New: I have plan variables to store the major and minor versions separately, as our deploy scripts handle major and minor upgrades differently, and the variables only seem to resolve to their value half of the time when generating a new release. Funny thing is, the variables always seem to work right when I click preview on the Release Versioning page.

            To reproduce, add a variable to plan, say build.foobar = works, run the plan and then attempt to make a release out of it using the using the variable $\{bamboo.build.foobar\} in the release name. It will work in the preview, but it will frequently not work when generating the release. As far as I can tell there is nothing different happening when it works vs. when it doesn't.
            James Dumay made changes -
            Labels New: radar

              Unassigned Unassigned
              0b35d968dd3e Sean O'Connor
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: