The clean-up is not working as expected. Is there a way to debug it, or otherwise determine why it is not cleaning up as expected?
Our clean-up policy and settings
Clean everything more than 180 days older than the last build
Clean history more than 90 days older than the last build
Clean artifacts more than 5 days older than the last build and older than the 1st successful build
Prevent dependency artifacts cleanup
This is hte default policy. Our build configs do not override the defaults. Clean-up is set to run daily.
Rules 1 and 4 seem to be working fine.
Rule 2: Clean history more than 90 days older than the last build
Most of our build configs show history as far back as June 2011. Taking one build config as an example, the oldest build is from June 23 (as seen in the history). The last successful build was yesterday, October 26, making it 125 days.
There are 153 builds that should have been cleaned up already, but are not. (Builds older than 90 days, that ran between June 23 and August 27.)
The build config has no artifacts and no dependencies whatsoever.
Rule 3: Clean artifacts more than 5 days older than the last build and older than the 1st successful build
We have a build config producing some artifacts. No-one depends on these artifacts, yet we have a long history of them (it was several months - I don't have an exact number since I have deleted them now). The last successful build is from today. Presuming the answer to this question is (A), I would expect the oldest artifact to be from last week.
To reiterate: Is there a way to debug the clean-up, or otherwise determine why it is not cleaning up as expected?