|
(Added SQLServer Section)
|
(Added section about multiple statuses.)
|
| Line 80: | |||
| ''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.)'' | ||
| + | ==== With Different Actions ==== | ||
| + | '''Q: OK, makes sense. But what if I have two statuses assigned with the same settings, except different actions?''' | ||
| + | ''A: Anthill seems to "play it safe" when considering build lives for deletion. So if you have both Delete & Inactivate set across the statuses, Anthill will '''inactivate''' the build life. If you have Delete & Archive, Anthill will '''archive'''. Inactivate & Archive would make it '''archive'''. Delete & Delete...hey, nice try smarty pants; it's going to '''delete'''. | ||
| === Dependency Considerations === | === Dependency Considerations === | ||
