Package publisher leaves a copy of the package in the artifacts folder (Bug #294)
When an outputDir is defined, the package file is moved there, as expected.
However, unexpectedly, a copy of the .zip file is left behind in the artifact folder. Since we have quite large package files, our build server runs out of disk space faster than expected.
I've filed this as a bug, since I don't expect a copy to be left behind if an outputDir is set. Correct me if I'm wrong.
You can always define multiple artifactcleanup publishers :
1<!-- cleaning buildlogs --> 2 <artifactcleanup cleanUpMethod="KeepLastXBuilds" cleanUpValue="50" /> 3 4<!-- cleaning the packages --> 5 <artifactcleanup cleanUpMethod="KeepLastXSubDirs" cleanUpValue="0" />
This solves the problem of the clean up :-)
It could be that the outDir provides an extra output folder, I do not know what the initial intent was.
It does sound logical that if outdir is specified, the package would be placed there.
I made a test run, and the zip file is placed there, but not the packages.xml file :-$
Is this another bug?
Also, the package zip file is copied to the output folder without any version information, so it will always be the package of the latest build.
Is this also the idea?
this needs some thinking over I guesss
- Status changed from New to Feedback