|
(Adding link so people know what an 'AND GATE' is.)
|
(Adding more information from SP-15518)
|
| Line 79: | |||
| ''A: In the case that a build has multiple statuses, whichever is the longest criterion out of the statuses that are assigned will take precedence. (i.e. if two statuses exist, one has 60 days one has 90 days, the build will not be cleaned up for 90 days, etc.)'' | ''A: In the case that a build has multiple statuses, whichever is the longest criterion out of the statuses that are assigned will take precedence. (i.e. if two statuses exist, one has 60 days one has 90 days, the build will not be cleaned up for 90 days, etc.)'' | ||
| + | === Dependency Considerations === | ||
| + | '''Q: What about builds that could potentially be active dependencies?''' | ||
| + | ''A: Dependencies do have an influence on cleanup behavior. If a build life was to meet the criteria to be cleaned up, but one of its dependencies is still active, the build life will not be cleaned up because it will be flagged '''in use'''. The dependency would have to meet its cleanup criteria (e.g. ''be inactivated/deleted''), and then the original build life that meets the criteria will be freed up to be cleaned as well.'' | ||
| == Searching Execution Information About Cleanup Settings == | == Searching Execution Information About Cleanup Settings == | ||
| '''Q: Where can I locate more information to see if cleanup is actually running, and view the output of the cleanup jobs?''' | '''Q: Where can I locate more information to see if cleanup is actually running, and view the output of the cleanup jobs?''' | ||
