I propose that the the artifacts are limited in an individual configuration by configuration case.
So that if the "archive days to keep" is set, this follows normal rules and keeps artifacts for that period.
For "archive number to keep" this would be applied to each configuration so that the last X sets of artifacts are kept for each configuration. This would mean that disabled configurations would maintain that amount of artifacts (assuming they are not removed by other rules).
This is slightly different to what occurs with the builds which removes the individual configuration builds only if the parent does not have a matching buildnumber.
I propose to extend the LinkedLogRotator to accept "archive days to keep" and "archive number to keep" values, and on the perform call the super class to handle these. while the builds are handled as current code.
I propose that the the artifacts are limited in an individual configuration by configuration case.
So that if the "archive days to keep" is set, this follows normal rules and keeps artifacts for that period.
For "archive number to keep" this would be applied to each configuration so that the last X sets of artifacts are kept for each configuration. This would mean that disabled configurations would maintain that amount of artifacts (assuming they are not removed by other rules).
This is slightly different to what occurs with the builds which removes the individual configuration builds only if the parent does not have a matching buildnumber.
I propose to extend the LinkedLogRotator to accept "archive days to keep" and "archive number to keep" values, and on the perform call the super class to handle these. while the builds are handled as current code.