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

Build Expiry Issue

Cameron Ferguson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 30, 2012

I am working with our Build Expiry settings for the first time with our bamboo setup. I am configuring it per plan, not globally -- so global build expiry is disbaled.

I am overriding one of our testing plans to enable the removal of Build Results. I am setting the time field to 0 to ignore. and I set Min Number of Builds to Keep to 10. (currently the plan has about 389 build results). I am basically wanting to keep the last 10 builds.

Using this wiki page for help: http://confluence.atlassian.com/display/BAMBOO/Configuring+Expiry+of+a+Plan%27s+Job+Build+Results

Now to me, "Minimum Builds to Keep" seems like a typo.. according to the Wiki page description, I think it would say "Maximum Builds to Keep" -- however the description in the wiki clearly states:

To keep a specified (or minimum) number of Job build results of this Plan,

  • In the 'Expiry period' field, specify '0'.
  • In the 'Minimum builds to keep' field, specify the number of Job build results of this Plan you want to keep. E.g. specify '50' to keep the latest 50 Job build results.

However, after saving nothing happens. Old results are not pruned. I have even re-ran the plan in order to possibly trigger the removal and still nothing. All 389 results are still available.

I am expecting I am doing something wrong or misunderstanding the wiki. I am only wanting to keep the last 10 builds.

Thanks in advance for the help

1 answer

1 accepted

0 votes
Answer accepted
Cameron Ferguson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 30, 2012

Ok I figured it out. The wiki page I linked in the original question should explain this as a step.

Build Expiry MUST still be enabled in the admin section, but you can still disable global expiry. Then there are cron settings for time intervals where the cron job is run and then each individual plan that has overriden the globla build expiry settings will be run as well.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events