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
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We set an individual plan Expiry like this:
Minimum builds to keep (set to "0") build(s) per plan '1' will keep the last build on a plan, the rest will expire according to your expiry time frame. Leave blank if not needed. Keep builds with the following labels (set to "keep") Enter multiple labels separated by spaces. Minimum deployments to keep (set to "2") successful deployment(s) per environment.
Problem: after some time has passed the Release cannot be found to be deployed even with the "keep" label by the Deployment project. We are on Bamboo 188.8.131.52 build 51513. I am selecting "Promote existing release to this environment" and I am receiving "No matches found" but when I go to the build plan I can see the build marked with a "keep". Are we doing something wrong with our individual plan Expiry settings above?
"Promote existing release to this environment" will fail if the existing release has been expired.
Minimum deployments to keep (set to "2") successful deployment(s) per environment.
This setting will only keep the latest 2 "successful" releases per environment. If the release is just created without any deployment performed, it is not considered as successful deployment yet causing the release to be expired.
Bamboo 6.3+ has revamped it so that release will not be expired if the related build is protected ("keep" label). BAM-17743
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.