20
Customers have installed this add-on in at least 20 active instances.
    by Mibex Software GmbHAtlassian Verified
    Mibex Software GmbH is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for Bitbucket Server 3.0.0 - 3.11.6
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Mibex Software GmbH supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    A Stash hook that instantly deletes the plan branch in Bamboo after the corresponding branch is deleted in Stash

    A Stash hook that instantly deletes the plan branch in Bamboo after the corresponding branch is deleted in Stash

    A Stash hook to keep your Bamboo build plans clean

    No more expired or disabled plan branches

    Restrict clean-up of plan branches with a regex

    Shipped as a Stash hook, this add-on instantly removes plan branches in Bamboo whenever the corresponding branch is deleted in Stash. This is useful for companies that make heavy use of branches.

    By instantly cleaning up plan branches, this add-on prevents cluttering the Bamboo UI and the logs with disabled plan branches and saves you valuable Bamboo resources.

    If you want to restrict the clean-up of your plan branches, you can configure this hook with a regex. Then, only when a matching branch is deleted (e.g., feature/**), this hook will delete the corresponding plan branch.

    More details

    Addresses the Bamboo issues BAM-13129, BAM-14229 and BAM-14869.

    Please note that due to technical issues with how application links work in versions >= 4.0.0 of Stash / Bitbucket Server, this plug-in cannot be supported for these versions and will therefore only work for versions < 4.0.0. Please try our free and open source plug-in Plan Branch Terminator for Bamboo instead.

    User reviews

    (3)
    Sign in to write a review »
    by Robert Dailey on 2015-02-03
    Really solid extension and works great. Worked with them on a bug I had and I got very quick response times. They were very nice and had the issue resolved in less than a week!
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Eclipse Support on 2015-02-02
    Is it possible to trigger branch plan deletion on multiple plans? The way we set up our plans we have multiple bamboo plans sharing the same Stash repository.
    Was this review helpful?YesNo

    Mibex Software GmbH

    Hi, thanks for your interest into Plan Branch Terminator for Stash. Multiple plans for the same Stash repository are currently not supported. But it is definitely something we would like to implement. Would you please create a feature request on our JIRA instance (https://mibexsoftware.atlassian.net/browse/TERMINATOR)? This lets you track the progress of the feature request and we can inform you as soon as we have implemented this. And we would also like to discuss possible solutions with you.
    by Terry Leung on 2014-12-11
    What if I have several feature branch in a repository? If I terminate 1 of the feature branch, and in the hook it set to delete all of "feature/**" branch plan, then is it going to delete all my other branch plan that is still valid?
    Was this review helpful?YesNo

    Mibex Software GmbH

    Thanks for your question. No, it will only delete the ONE plan branch when the corresponding branch is deleted in Stash. The field "Branch patterns for plan branch deletion" is just to specify the branches that are considered for deleting plan branches. Say you enter "feature/**" in the hook settings, and the branch "feature/new-settings-dialog" is deleted because you merged it in "develop" and have chosen to delete the source branch, then this add-on will delete the corresponding plan branch in Bamboo. But if you delete the branch "releases/release-1.0", then it will NOT delete the corresponding plan branch because this one does not match the pattern "feature/**". We will try to make the highlights more clear concerning this.

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    The add-on tier should match the licensed user tier of the Atlassian host application. For example, if you have a Confluence Server license for 25 users, you should purchase the 25-user tier for add-ons. Even if fewer users want to use the add-on than your host application license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    Support

    Mibex Software GmbH is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Mibex Software GmbH supports Plan Branch Terminator for Stash. You can visit the support site to get help.

    Get support

    Versions

    Version 1.1.1 Bitbucket Server 3.0.0 - 3.11.6 Released 2015-02-19

    Summary

    Improved validation error messages and bugfixing

    Installation

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Plan Branch Terminator for Stash via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Plan Branch Terminator for Stash. You're prompted to log into MyAtlassian. Plan Branch Terminator for Stash begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Bitbucket instance.

    To find older Plan Branch Terminator for Stash versions compatible with your instance, you can look through our version history page.

    Similar add-ons