A "build plan" that had a failed Job that was later disabled on the Plan configuration, will run endlessly until force-paused if "Rerun failed/incomplete jobs only"

XMLWordPrintable

    • 2
    • Severity 2 - Major

      Problem

      A "build plan" that had a failed Job that was later disabled on the Plan configuration will run endlessly until force-paused if "Rerun failed/incomplete jobs only", though the build reports itself as "Successful/Completed "

      Environment

      Bamboo 8.2

      Steps to Reproduce

      1. Create a Plan with two successful Jobs
      2. Run a new build
      3. Modify the second and last Job and force it to fail (exit 1)
      4. Run a new build
      5. Disable the failed Job on the Plan
      6. Rerun the failed build for "failed/incomplete jobs only"

      Expected Results

      1. The build should skip the Disabled job and succeed

      Actual Results

      1. The build skips the Disabled job, and reports the build as "Completed" but breaks the build queue with a state problem leaving the Build as "running" endlessly.
      2. No new runs of the same Plan are allowed if Concurrency=1

      Workarounds

      Option 1:

      • Stop the running build manually (click on the Stop button).

      Option 2:

      • Use the Bamboo REST API to delete the build from the queue:
        $ curl -v -u admin:admin -k -X DELETE 'https://<Bamboo_URL>/rest/api/latest/queue/{projectKey}-{buildKey}-{buildNumber}'
        

      It is known and noticed that the build timings will be considered up until the build is removed from the queue.

      Notes

            Assignee:
            Krzysztof Podsiadło
            Reporter:
            Eduardo Alvarenga (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: