Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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 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 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
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you