-
New Feature
-
Resolution: Unresolved
-
Major
-
None
Hello, thanks for the nice Clover plugin! One issue we are experiencing is that since enabling the clover plugin, we are running out of disk space all the time because it seems to create gigantic directories in jobs/$CLOVER_JOB/builds for each build, because it archives the html reports and perhaps some code as well for each build.
Having the coverage percentages available is great, as well as the trend, but after enabling Clover each build seems to be about 600MB which is quite a problem. It would be great if there was an option (perhaps default) to only keep artifacts for the most recent build, so you can still have the trend data and see the percentages but not keep around all the artifacts from the build.
For now I will write a script to clean out everything clover seems to be archiving for all but the most recent build and run it nightly. Thanks for any insight!
Actually after further investigation I wonder if this is being exacerbated by another issue, where if you have an index.html in your workspace root (and maybe also if the xml file you point clover at is also in the workspace root), the Clover plugin will think your entire workspace is the html to archive and recursively archive the entire workspace for each build. Any ideas?