| << Back to previous view |
|
[QB-2900] Enhanced Artifact and Build Pruning
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | J. Mash | Assigned To: | Robin Shen |
| Resolution: | Duplicate | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
This is a request to enhance the existing artifact and build pruning mechanism to allow for greater control and flexibility over how things get cleaned up.
1. Add a cleanup strategy to allow artifacts to be cleaned up based on pipeline status. - The use case here is that, the further into a pipeline a build gets, the longer the artifact should be kept around. 2. Add an option to keep a minimum number of artifacts around, regardless of whether the criteria says an artifact/build should be cleaned up. - The use case here is that we have several products that build maybe twice a year and depend on artifacts that we build, so if we don't specify the cleanup strategy to be something like 1+ years, artifacts will get cleaned up out from underneath them. This feature would allow us to say "clean up all but the most recent 3 artifacts/builds". 3. In much the same way as we can currently define multiple criteria for a build notification or promotion to be triggered, it would be nice to allow multiple conditions under which artifacts / builds would be cleaned up. - The use-case here is that we want to have failed builds (and artifacts that are the product of failed builds) to be cleaned up much sooner (30 days) than artifacts from successful builds (1+ year), and this feature would enable that scenario. Please feel free to reach out if there are any questions. |
| Comments |
| Comment by Robin Shen [ 22/Jan/18 11:07 PM ] |
|
With |