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

Pass the build-specific variables automatically into environment variables (like plan/global variables do)

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Steps to reproduce:

      1) create plan, script task:

      echo $bamboo_buildResultKey
      echo $bamboo_buildNumber
      

      2) run the plan
      3a) expected result (in the logs) is to see something like

      PROJ-PLAN-JOB1-1
      1
      

      3b) while current behavior is:

      
      

      (these environment variables are undefined, that's why we see empty logs)

      Seems we pass the plan/global variables into the environment:

      But we don't do that for built-in variables like:

      • ${bamboo.buildPlanName}
      • ${bamboo.buildKey}
      • ${bamboo.buildNumber}
      • ${bamboo.buildResultKey}
      • ${bamboo.buildTimeStamp}
      • ${bamboo.repository.revision.number}
      • ${bamboo.build.working.directory}
        etc...

              mgardias Marcin Gardias
              pstefaniak PiotrA
              Votes:
              85 Vote for this issue
              Watchers:
              61 Start watching this issue

                Created:
                Updated:
                Resolved: