Can we make scheduled Bamboo plan always enabled?

Question

Hello,

As we are new to bamboo executions,

We are facing the issue with Bamboo plan which we have scheduled for everyday execution. Bamboo plans are getting automatically disabled after every successful execution therefore next day scheduled run is unable to trigger automatically and we need to manually get it enabled each time.

Can anybody has related information/solution?

Thanks,

Nikhil

Eduardo Alvarenga · Answer

Hello @NikhilM

You need to focus on the cause of why the Plans are getting disabled as this is not expected in a normal environment. Insisting on automation to keep them enabled will not get the main issue sorted and may create even more issues.

Please focus on the cause by investigating if any of the causes I have previously listed are happening, and then take action.

As you have mentioned Specs, can you confirm if multiple changes are made to the plan? If a change to the Specs code fails the validation build, Bamboo will disable the Plan until the next Specs code validation build succeeds.

Regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

NikhilM_mgf2hw · Answer

Hello,

Thanks for your reply.

Actually, issue is we can't keep our Bamboo plans (Manual/Scheduled) always enabled as after every execution it's getting disabled.

I need solution for keeping Bamboo plan always enabled so that our scheduled plans will get executed without having manual interference. I am sure we need to do some configuration in specs (Java/Yaml) but do not know what configuration we need to change.

We tried below changes in Yaml file:

Old : buildHangingConfig.enabled: 'false'

Change : buildHangingConfig.enabled: 'true'

But it's not working so do you have any solution to resolve this issue.

Thanks,

Nikhil

Eduardo Alvarenga · Answer

Hello @NikhilM

Welcome to Atlassian Community!

Bamboo will only disable a plan on the following occasions:

* Manually (by the user)
* A plan change that sets it as disabled over Specs
* The linked branch is deleted on the VCS Repository
* A Pull Request that relates to a Plan branch is merged or rejected
* "Clean up plan branch automatically" in the configuration on the branch level is set. It is selected by default for manually created plan branches

As you have mentioned "successful execution" could that be because of a Pull Request merger?

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--