Bamboo plan shows as successfully run but actually does not get executed when the job/s are in disabled state

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Plans in Bamboo will show as successfully run when jobs are in disabled status. The plan will run when clicked on Run Plan / Run Customised but it does not actually get executed.

Environment

6.10.4

Diagnosis

To understand this issue when you are running the plan, the UI shows as executed by green bar but when you click on Logs tab, there are no logs displayed as seen in the below screenshot:

Also the atlassian-bamboo.log file you will show you the below log entries:

2021-09-09 10:58:13,628 INFO [6-DelayedChangeDetectionThread:pool-12-thread-39] [ChainExecutionManagerImpl] Plan PPD-NP-3: Plans Per Day - Number of plans has finished executing
2021-09-09 10:58:13,652 INFO [6-DelayedChangeDetectionThread:pool-12-thread-39] [PlanStatePersisterImpl] Updating delta states of build following PPD-NP-3
2021-09-09 10:58:13,704 INFO [6-DelayedChangeDetectionThread:pool-12-thread-39] [PostChainIndexAction] Indexing PPD-NP-3
2021-09-09 10:58:13,706 INFO [6-DelayedChangeDetectionThread:pool-12-thread-39] [DefaultBuildResultsIndexer] build result doesn't have buildDate, so ignored PPD-NP-3
2021-09-09 10:58:13,706 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-12] [DependencyChainListener] Checking children plans of [PPD-NP] for plan PPD-NP-3
2021-09-09 10:58:13,708 INFO [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-12] [DependencyChainListener] Finished checking children plans of 'Plans Per Day - Number of plans' for plan PPD-NP-3

Along with the above, below are the steps for more clarity as to when this issue effects you:

  • Create a plan, create a task in the default job.
  • Disable the default job and the plan.
  • Now Enable the plan and try to run.
  • The plan shows successfully execution on clicking Run Plan / Run Customised, but it actually does not run.
  • No build logs are seen in the UI as well.

Cause

There are times when you end up disabling the plan and also disable the jobs inside the plan, it could be one job or multiple jobs. But the issue occurs when you enable the plan and forget to enable the jobs. By default Bamboo does not enable the jobs when you enable a disabled plan. You will have to explicitly go inside the plan and enable the job/s.

Solution

To get to the solution, you can simply go to the particular plan and click on Configure Plan to see if all the jobs or any job is disabled. Alternatively you can also identify if the job is disabled by doing a Spec export of the plan with help of below steps:

  • Login into Bamboo (with admin user)
  • Navigate to the plan and click on Configure Plan
  • On the right side you will see Actions dropdown, select View plan as Java Specs and copy paste the Specs in any editor to view the plan as Java Spec. 
  • In this Specs, locate the below lines:

    .stages(new Stage("Default Stage")
                        .jobs(new Job("Default Job",
                                new BambooKey("JOB1"))
                                .enabled(false)
  • In the above, if you see the line .enabled(false) under the default/any other job, then this means the job is disabled.

  • Now please proceed on to enable the job/jobs and then run the plan.


Last modified on Sep 17, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.