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

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 3.3.3, 3.4 M1, 3.4
    • Affects Version/s: None
    • Component/s: 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.

            Assignee:
            PiotrA
            Reporter:
            Mads Nissen
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: