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.
I would like to know if possible:
A) Where i can determine the number of deployment projects to keep in Bamboo except from the global expiry settings section.
B) In addition, even if in the global expiry settings i configured to keep only the ((last)) 10 successful deployment projects, it shows me 25 instead of 10.
C) At last, and this is the most weird part, as the image shows above, Bamboo doesn't keep the last deployment projects that i am interested to keep, instead it keeps some old releases.
My global expiry settings are set like that:
A) Where i can determine the number of deployment projects to keep in Bamboo except from the global expiry settings section.
Unfortunately, there is no other place rather than the Global admin section where you set up Expiry at the global level in Bamboo. For this reason please find below some suggested requests raised to enhance the Expiry feature in Bamboo:
B) In addition, even if in the global expiry settings i configured to keep only the ((last)) 10 successful deployment projects, it shows me 25 instead of 10.
Based on the Expiry configuration provided (screenshot), you are telling Bamboo to expiry only "Build and release artifacts", meaning that you are leaving behind deployment logs, for instance. Therefore, you are seeing more entries than the ones you are expecting.
C) At last, and this is the most weird part, as the image shows above, Bamboo doesn't keep the last deployment projects that i am interested to keep, instead it keeps some old releases.
Please, review the Expiry configuration based on the comment provided on this thread. In case you continue on experiencing issues, I would suggest you on raising a Support Case with Atlassian, so you can provide them with more details about your Deployment, Environment and your Expiry settings can be reviewed.
Kind regards,
Rafael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.