[
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161908#comment-161908
]
Joshua Kugler commented on JENKINS-13554:
-----------------------------------------
This is affecting us too. jenkins-1.457-1.1.noarch RPM.
Plugins:
ant - 1.1
javadoc - 1.0
subversion - 1.33
parameterized-trigger - 2.13
git - 1.1.12
gerrit-trigger - 2.3.1
hudson-pview-plugin - 1.8
build-timeout - 1.8
maven-plugin - 1.457
analysis-core - 1.31
warnings - 3.22
doxygen - 0.9
plot - 1.5
copyarchiver - 0.5.1
confluence-publisher - 1.3
jira - 1.29
cvs - 1.6
global-build-stats - 1.2
scm-sync-configuration - 0.0.4
platformlabeler - 1.1
monitoring - 1.32.1
checkstyle - 3.21
disk-usage - 0.14
build-pipeline-plugin - 1.2.3
cppcheck - 1.0.2
libvirt-slave - 1.6
matrix-reloaded - 1.0.1
github - 0.7
analysis-collector - 1.18
iphoneview - 0.2
twitter - 0.6
promoted-builds - 2.4
copyartifact - 1.21
ssh-slaves - 0.21
translation - 1.8
join - 1.14
publish-over-ssh - 1.6
We also had promoted builds 2.4 activated, but I disabled that. I will check to
see if that made any difference.
> 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
