
Global lock for Bamboo plans
Global lock for Bamboo plans
More details
Do you have multiple plans that can not be executed in parallel?
You also want to use build agents (remote or not!) with those plans? You are stuck on that, right? π
Maybe you have some shared resources that are used by each build.
Maybe you created a single agent that can only run a built at a time to exclusively run those plans.
None of that sounds super great... (and probably that is why you arrived here!)
Fear no more!
Bamboo Global Plan Lock is here to help you overcome that! π
With this plugin, you can set a unique "locking key" for the plans that need to be executed sequentially and let them run in any agent you feel like. Each plan build will wait for the availability of the lock to proceed. And while it waiting for the lock it won't take up an agent slot! π
Give it a try! and tell you more about your experience at https://gitter.im/bamboo-global-plan-lock/community
Reviews for cloud
(2)Sign in to write a reviewReviews for server
(2)Sign in to write a reviewReviews for Data Center
(2)Sign in to write a reviewCloud Pricing
Server Pricing
Data Center Pricing
Basic support resources are available for this app.
Vendor support resources
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.2.0 β’ Bamboo Server 6.10.4 - 7.0.6 β’ Released 2020-08-18
Summary
Initial public release
Installation
- Log into your Bamboo instance as an admin.
- Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Global plan lock for Bamboo via search. Results include app versions compatible with your Bamboo instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
To find older Global plan lock for Bamboo versions compatible with your instance, you can look through our version history page.