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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In the global expiry settings in Bamboo i have set to keep at least 10 releases per environment(see image 1 below)
Image 1
Nevertheless, when i navigate to a certain deployment environment, it is detected that it keeps 25 releases(see image 2 below).
Why is that happening and how can i set how many releases i want to keep per environment except through the global expiry settings?
Image 2
Is the release-272 created more than 7 days ago?
The expiry will look for all releases created more than 7 days ago first to be expired. If there are a lot of releases expired due to 7 days condition causing the number to be less than 10 per environment, it will keep the latest 10 successful releases per environment.
Hello and sorry for my late reply. Yes the release-272 is older than 7 days. I understand what you mean about keeping the latest 10 successful releases per environment. But still as the image shows it keeps showing the last 25 releases instead of only the last 10.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the 25 releases are not older than 7 days, it will not be deleted.
Example 1:
Release 1 will be deleted. Release 2-5 are not deleted due to 10 successful deployments to be kept. Release 6-11 not more than 7 days.
Example 2:
Release 1-5 will be deleted. Release 6-17 (total 12) not deleted cause not more than 7 days yet.
If release-272 is older than 7 days but still not deleted now, it means there is a problem with the deletion process. Need to check the log during the deletion scheduled time.
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.