You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Does anyone have an idea of how to trigger an action when a build plan branch is automatically removed by Bamboo?
I've setup a branch build plan that also deploys each branch to Tomcat by adding the branch name to the context name, like website-branch1, website-branch2 which works fine.
But when the branch is deleted in BitBucket and Bamboo automatically deletes the branch from the build plan, the deployed instance of the branch is still in tomcat.
I could write code to query the build plan for the branches, keep it as an external list and anytime it finds one that is no longer in bamboo delete that one from tomcat and remove it from the list.
Is there a better way to do it?
Deployment is done by a build and there is no build triggered when a branch is deleted. So, you need to do it either by maintaining it externally or in a Bamboo add-on that captures branch deletions.
What is your title suggesting about a limitation of 5 branches? That is not the case in Bamboo. Unless you have some expiry rules set up, branches won't be automatically removed. When a bitbucket branch is deleted, the corresponding Bamboo branch will be deleted though.
Title was an accident, I corrected it. Having an issue with IE.
I know the deletion doesn't trigger a build, was trying to find information on events.
Looking into it further I found some information on Bamboo Event Listeners. It documents a BuildDeletedEvent and MutipleJobsDeletedEvent which is probably what I'm looking for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that is what you need. You will need an add-on that implements a listener for that event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.