Add options to disable Bamboo plugins during startup

Problem Definition:

1) In some cases, Bamboo would not be able to startup due to a specific plugin that is installed in the instance. Then, we would need to startup the instance by moving the plugins out of the caches/plugins folder manually before starting up Bamboo to make sure that the instance at least is accessible.

This is the current steps to start Bamboo in safe mode:

1. Stop Bamboo
2. Navigate to <bamboo-shared-home > plugins folder
3. Rename the plugins folder to anything else
4. This will make Bamboo create the folder again
5. Start Bamboo

Then, nothing will be initialized as the folder empty and Bamboo starts in safe mode. But, this is not exactly simple to perform.

2) Another option is to run the below query and find the details related to the plugin which you want to disable

select * from bandana where bandana_key like 'bamboo.plugin.state'

Details would be displayed like below from the column serialized_data

<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 as false for the plugin which you want to disable from the column serialized_data
For any DB update queries, make sure to to take backup of the tables.

Suggested Solution

To have a specific flag that will make Bamboo to startup in safe mode without making changes in that folder.

• First flag to make Bamboo startup in a safe mode
• Second flag to disable a specific plugin by passing the class name of the plugin.