Summary

When Bamboo is started, some plans and deployment environments start to execute based on their respective triggers. It is possible to start Bamboo and prevent certain actions from happening. There are many reasons why someone would do this (e.g. troubleshooting, migration, testing upgrade, and etc). In this article we'll cover the following actions that can be disabled during the Bamboo startup process:

1. prevent build plans and deployment environments from getting automatically triggered
2. branches from getting created
3. build statuses from being sent over to Bitbucket

Solution

Add one or more of the following JVM options to the JVM_SUPPORT_RECOMMENDED_ARGS variable, steps on how to do this in Java setting properties. 

Disable automatic build plan and deployment environment execution 

This will prevent builds and deployment environments from getting automatically triggered based on new changes happening in the respective default repositories only – manual builds and deployments can still run.

-Datlassian.bamboo.build.disable=true

Disable branch detection

This will prevent Bamboo from looking for new or deleted branches in any plan's default repository. In other words, new plan branches are not created and old plan branches are not disabled based on the changes in the respective repository. However, this option doesn't prevent starting a build manually.

-Datlassian.bamboo.branch.detection.disable=true
-Datlassian.bamboo.closed.branch.detection.disable=true

Disable build status updates to Bitbucket

This will prevent Bamboo from sending any build status update notifications to the Bitbucket server.

-Dbamboo.stash.disable.build.status.updates=true

BAMBOO 8.2+ Disable automatic fallback to polling for Bitbucket Server, even if Application Links don't work or the Bitbucket Server plugin is disabled

This is only available on Bamboo 8.2 and later releases:

-Dbamboo.disable.stash.polling=true

After adding those settings, restart Bamboo and verify the settings.