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

Plan variables don't seem to make it to deployment projects reliably

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • High
    • None
    • None
    • None
    • None

    Description

      I have a number of projects which I deploy to multiple AWS environments. The deployment process is identical, save for which environment it goes to, and project-specific details.

      As such, I put the project-specific details into the Bamboo build plan as variables, and the environment-specific details into the deployment environment as variables. The tasks then are "cut-and-paste" for uniformity.

      This all works great when I create a release from builds that I triggered manually in Bamboo. However, when I create a release from an automatically triggered build, these custom plan variables aren't passed down.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ae68c5fad4e9 Robert Watkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: