How to start Bamboo with all or few external apps disabled
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
The purpose of this page is to explain ways in which Bamboo can be started with all the external plugins disabled or just a few of them.
Sometimes while restarting Bamboo a few of the external plugin fails to start which leads to cascading effect of failure of system plugins due to which Bamboo does not start.
There has been a feature request raised to provide a JVM flag in Bamboo which would do the following, kindly refer BAM-22418 - Add options to disable Bamboo plugins during startup for more details
First flag to make Bamboo startup in a safe mode - With all plugins disabled
Second flag to disable a specific plugin by passing the class name of the plugin.
Solution
Solution 1 :
Please follow the below steps in Bamboo server.
Stop Bamboo
Navigate to <bamboo-shared-home > plugins folder
Rename the plugins folder to anything else
This will make Bamboo create the folder again
Start Bamboo
Solution 2 :
If the solution 1 does not work for you, you can try the below approach from Database side
Another option is to run the below query and find the details related to the plugin which you want to disable
1
select * from bandana where bandana_key like 'bamboo.plugin.state'Details would be displayed like below from the column serialized_data from the result of the above query, serialized_data column would contain the details of all the other plugin, in my example below I am sharing one of the plugin details which I want to disable
1
2
3
4
5
6
7
8
9
10
11
12
13
<com.atlassian.plugin.manager.DefaultPluginPersistentState>
<map class="java.util.Collections$UnmodifiableMap">
<m>
<entry>
<string>io.qameta.allure.allure-bamboo</string>
<com.atlassian.plugin.manager.PluginEnabledState>
<enabled>true</enabled>
<timestamp>1688737505717</timestamp>
</com.atlassian.plugin.manager.PluginEnabledState>
</entry>
</m>
</map>
</com.atlassian.plugin.manager.DefaultPluginPersistentState>Set <enabled>false</enabled> for the plugin that you want to disable from the column serialized_data
Post doing the above step restart Bamboo, Bamboo should come up with the specific app disabled.
Please make sure to take backup of BANDANA table before changing any data as per the results above.
Was this helpful?