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

Rebuilding a plan causes variables to fail substitution from deployment project

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 5.7.0
    • 5.6.2
    • None
    • None

    Description

      Plan Foo is linked to Deploy project Bar. Let's say build #123 is the next build.
      Deploy project Bar has a Script task that references a plan variable of Foo, like echo ${bamboo.some.plan.variable.of.importance}

      Scenario:

      • Start building Foo 123.
      • Cancel Foo Build 123.
      • From Foo Build 123, run > rerun incomplete jobs
      • Foo Build 123 completes successfully.
      • From Deploy project Bar, run deploy on 123
      • Bar 123's task does not substitute the value.

      Workaround:

      • Simply do not rebuild. If you start Foo 124, and do not cancel / rerun, Bar 124 will correctly have the plan variables accessible for substitution.

      Of note:

      • Global variables continue to be interpreted. It is only plan variables that are not present.
      • The plan variable that fails substitution in the Bar deployment project is present on Foo 123's metadata tab.
      • I am using the Maven POM value Extractor plugin, which may or may not have interaction with this issue. (It actively sets plan variables each run)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e3b50d08b0c3 Eric Fusciardi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: