[JIRA] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained

3 views
Skip to first unread message

a.regentov@ftc.ru (JIRA)

unread,
Oct 28, 2015, 9:01:04 AM10/28/15
to jenkinsc...@googlegroups.com
Andrey Regentov commented on Improvement JENKINS-23066
 
Re: Allow cleaning up parts of Jacoco report artifcats retained

Just the same here. Very much space eaten on disk by jacoco (like 30M per build, hungreds of builds), don't want to dive deep into old coverage reports, but want to see the historical graphs only.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

marcosholgado@gmail.com (JIRA)

unread,
Feb 16, 2016, 8:42:02 AM2/16/16
to jenkinsc...@googlegroups.com

Same problem here, 36MB per build and want to see just the historical graphs.

zhh205@gmail.com (JIRA)

unread,
Apr 4, 2016, 4:43:02 AM4/4/16
to jenkinsc...@googlegroups.com

Same here. Does anybody have a workaround in the mean time?

nfalco79@hotmail.com (JIRA)

unread,
Apr 22, 2016, 9:30:02 AM4/22/16
to jenkinsc...@googlegroups.com

Me too.
In addition due actually limitation of plugin to describe which source folder should be keept, for a tycho-maven build for example, we specify something like /src//,
all files in these folder (source and resources like .xml .pdf .js .html .jps .gif.....) are copied to jobs/JOB1/builds/$BUILD_ID/jacoco/sources, gathering about 2.2GB for each build.
I think plugins should collect only files that matches entry in .exec file and/or permit a better selector on which resources have to copy.

Actual workaround add a shell script that delete sources folder in jacoco folder for previous build.

export BUILDS_FOLDER=`dirname $WORKSPACE`/builds

for folder in `ls $BUILDS_FOLDER | grep "[0-9]\{1,\}" | grep -v $BUILD_ID`; do
    echo Deleting "$BUILDS_FOLDER/$folder/jacoco/sources" ; rm -rf "$BUILDS_FOLDER/$folder/jacoco/sources" ;
done;

michiel.hendriks@mp-objects.com (JIRA)

unread,
May 27, 2016, 11:15:01 AM5/27/16
to jenkinsc...@googlegroups.com

This disk eating feature makes the plugin pretty much unusable for us. Build jobs went up from around 70MiB to over 900MiB.

The classes directory is close to 500MiB even though the actual produced class files is less than 100MiB.
It's storing files more than once is different directories, once per path element:

./SomeCensoredClass.class
./action/SomeCensoredClass.class
./shipmenttype/action/SomeCensoredClass.class
./control/shipmenttype/action/SomeCensoredClass.class
./oms/control/shipmenttype/action/SomeCensoredClass.class
./foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class
./com/foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class

michiel.hendriks@mp-objects.com (JIRA)

unread,
May 27, 2016, 11:17:02 AM5/27/16
to jenkinsc...@googlegroups.com
Michiel Hendriks edited a comment on Improvement JENKINS-23066
This disk eating feature makes the plugin pretty much unusable for us. Build jobs went up from around 70MiB to over 900MiB.

The classes directory is close to 500MiB even though the actual produced class files is less than 100MiB.
It's storing files more than once is different directories, once per path element:

{code}

./SomeCensoredClass.class
./action/SomeCensoredClass.class
./shipmenttype/action/SomeCensoredClass.class
./control/shipmenttype/action/SomeCensoredClass.class
./oms/control/shipmenttype/action/SomeCensoredClass.class
./foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class
./com/foobarquux/oms/control/shipmenttype/action/SomeCensoredClass.class
{code}

The same happens in the source directory. So there is something seriously wrong with copying the files.

michiel.hendriks@mp-objects.com (JIRA)

unread,
May 27, 2016, 11:45:02 AM5/27/16
to jenkinsc...@googlegroups.com

Ignore my previous comment.
I had a config error, I had a trailing ** one of the paths.

moshe.zvi@gmail.com (JIRA)

unread,
Nov 7, 2019, 1:10:03 PM11/7/19
to jenkinsc...@googlegroups.com

+1

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages