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

If source code task is not in a job then bamboo.repository.revision.number is not set (even if its available in previous jobs)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 3.3.3, 3.4 M1, 3.4
    • None
    • None
    • None

      When a sourcecode task is done in the 1st stage, and not in a later stage the bamboo.repository.revision.number is not set for the jobs in the later stage.

      This is impractical as the later jobs might need this variable.

      Could work around it if it was possible to set the bamboo.repository.revision.number into a plan variable in the first stage.

              pstefaniak PiotrA
              36bf93b98be7 Mads Nissen
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: