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

Plan variable values are not getting substituted for deployments when triggered by repository

    XMLWordPrintable

Details

    Description

      Steps to reproduce:
      1. Create a plan variable under the variables tab of the plan (Ex.:thisisatest)(Screenshot: DefineTheVariable.PNG)
      2. Create a deployment project that gets triggered after the completion of this plan
      3. Use the custom plan variables in tasks under both the plan and deployment project tasks
      4. If the plan is triggered from the repository(Git in this case), having the "Repository triggers the build when changes are committed" selected, the variable value shows up for the build but not for the deployment
      5. If I run the build manually, the variable gets substituted for both the build and the deployment
      Please check the attached screenshots. Release-4 is the manual run, Release-5 is triggered by repo.

      Attachments

        1. BuildLogsManual_1.PNG
          BuildLogsManual_1.PNG
          89 kB
        2. BuildLogsTriggered_1.PNG
          BuildLogsTriggered_1.PNG
          91 kB
        3. DefineTheVariable.PNG
          DefineTheVariable.PNG
          83 kB
        4. DeploymentLogsManual_2.PNG
          DeploymentLogsManual_2.PNG
          125 kB
        5. DeploymentLogsTriggered_2.PNG
          DeploymentLogsTriggered_2.PNG
          122 kB
        6. DeploymentVariablesTabManual_2.PNG
          DeploymentVariablesTabManual_2.PNG
          95 kB
        7. DeploymentVariablesTabTriggered_2.PNG
          DeploymentVariablesTabTriggered_2.PNG
          86 kB

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. BAM-13644 Automated Builds: Plan variables disappearing in Deployment Tab

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. BAM-13793 plan variables not available for use in deployment after automated builds

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. BAM-13735 Plan variables don't seem to make it to deployment projects reliably

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. BAM-13739 Deployment variables aren't being exported to scripts

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. BAM-13583 Plan variables in release versioning does not work when deployment triggered by a scheduled build

          • Low - Low priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. BAM-13549 Custom plan variables do not seem to resolve to their values consistently when generating a release

          • High - High priority issues
          • Closed
          is cloned from

          BDEV-3235 Loading...

          Activity

            People

              pstefaniak PiotrA
              ssetayeshfar Sepideh Setayeshfar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: