This app has been archived

You may still get support information and download previous versions of this app. Learn more.
Last modified 2019-01-08 0 downloads By Mibex Software Labs

Support

To check known issues (or if you want to file one), view this app's issue tracker.


To learn more about the app, you should:

    Description

    No instant deletion of plan branches


    While Bamboo allows the automatic deletion of plan branches, this does not happen instantly when a Git branch gets deleted. Also, there is no possibility to configure the plan branch deletion settings globally.



    Expired / disabled plan branches clutter up the UI


    For teams that make heavy use of branches, disabled plan branches can clutter up the Bamboo UI and waste resources. And they count as full plans in terms of the license limit which can be important for small teams.



    This add-on deletes plan branches instantly


    This add-on instantly removes plan branches in Bamboo whenever the corresponding Git branch is deleted in Stash / Bitbucket server. And there is no configuration necessary!



    More details


    While Bamboo allows the automatic deletion of plan branches since version 5.9 (see feature request BAM-13129), this does not happen instantly when the source branch of a repository a plan branch targets is deleted. Instead, the deletion is executed during a configurable clean-up job. Until the final deletion, the plan branches will remain as inactive entities in the Bamboo plan. Also, there is no global configuration point available, so you have to configure this for every plan of your Bamboo instance separately.

    This is where our open source plug-in comes in: without any configuration efforts it will delete plan branches instantly.

    Word of caution: deleting a plan branch will irrevocably delete all configurations, artefacts, logs etc. related to this plan branch! Please also note that - even though we have tested this plug-in carefully - its use is at your own risk. So please use this in one of your testing environments first before adapting it on your production instance.

    Version history