Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,883
Community Members
 
Community Events
184
Community Groups

How can i set how many releases i want to keep per environment in Bamboo

In the global expiry settings in Bamboo i have set to keep at least 10 releases per environment(see image 1 below)

Image 1

image1.png

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

image2.png

1 answer

0 votes
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 08, 2018

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.

Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 14, 2019

If the 25 releases are not older than 7 days, it will not be deleted.

Example 1:

  1. Release 1 - 11 days
  2. Release 2 - 10 days
  3. Release 3 - 9 days
  4. Release 4 - 8 days
  5. Release 5 - 7 days
  6. Release 6 - 6 days
  7. Release 7 - 5 days
  8. Release 8 - 4 days
  9. Release 9 - 3 days
  10. Release 10 - 2 days
  11. Release 11 - 1 day

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:

  1. Release 1 - 11 days
  2. Release 2 - 10 days
  3. Release 3 - 9 days
  4. Release 4 - 8 days
  5. Release 5 - 7 days
  6. Release 6 - 6 days
  7. Release 7 - 5 days
  8. Release 8 - 4 days
  9. Release 9 - 3 days
  10. Release 10 - 2 days
  11. Release 11 - 1 day
  12. Release 12 - 1 day
  13. Release 13 - 1 day
  14. Release 14 - 1 day
  15. Release 15 - 1 day
  16. Release 16 - 1 day
  17. Release 17 - 1 day

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events