I don't particularly care about having a single artifact cleanup publisher vs multiple ones. That's no different than a filemerge task for instance.
But your point about adding more settings is defintiely valid. On Nov 21, 1:12 am, "Ruben Willems" <[EMAIL PROTECTED]> wrote: > Hi > > You're right in all cases : > you can use multiple artifact cleanup publishers > > I made this first with the ability to > remove builds older than X, or to keep X amount of builds. > > But later on I added other cleanup settings. > maybe it is better to foresee that you can specify multiple settings within > 1 > ArtifactCleanup publisher element. But his will be a breaking change for the > next release. > > Are there other people who want the new layout? > > If there are more settings added to this publisher, it is indeed better to > change it. > > with kind regards > Ruben Willems > > > > On Thu, Nov 20, 2008 at 4:57 PM, Mark <[EMAIL PROTECTED]> wrote: > > > Can there be multiple artifact cleanup publishers? Reading the docs, > > I'm confused over how the internals of the publisher might work. For > > example: > > > <artifactcleanup cleanUpMethod="KeepLastXBuilds" > > cleanUpValue="50" /> > > > I realize that this will keep the latest 50 builds, but will this also > > remove modification history information stored by the > > modificationHistoryPublisher? I could do this: > > > <artifactcleanup cleanUpMethod="KeepMaximumXHistoryDataEntries" > > cleanUpValue="50" /> > > > to keep 50 history entries, but that won't remove builds -- at least I > > don't think so. > > > Can/should I put both of these cleanup publishers in my config file, > > or can I have only one? Does the KeepLastXBuilds also cleanup the > > history data entries? > > > Thanks in advance!- Hide quoted text - > > - Show quoted text -
