stibbons created JENKINS-13554:
----------------------------------
Summary: Re: Matrix jobs does not automatically remove old
artifacts for configurations
Key: JENKINS-13554
URL: https://issues.jenkins-ci.org/browse/JENKINS-13554
Project: Jenkins
Issue Type: Bug
Components: disk-usage, matrix
Reporter: stibbons
Assignee: vjuranek
Priority: Critical
Hello
I'm reporting an important issue on Jenkins with matrix build. The 'Discard Old
Builds' setting doesn't remove builds in configuration, leading to increase
disk usage without limit.
Here is the behavior :
- the master job is correctly cleaned, for instance, after a month if
configured so, the artifacts are dropped and the build are correctly deleted
- however this is not the case for the configuration builds, if i go into the
page of one I can see a very long list of builds not having been deleted (so
this is not synchronized with the 'master').
The files in
~/jenkins/jobs/MyJobName/configurations/axis-FOO/foo/axis-BAR/bar/builds
are no deleted while
~/jenkins/jobs/MyJobName/builds/
are correctly deleted.
Also, disk usage is not correctly computed in the disk usage space : the size
of the configuration are not taken in account.
This leads on my build machine a complete saturation of the disks after 1 week
of work. I think this is a very critical issue.
Thanks,
Gaetan
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
