[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2013-03-19 Thread stevencrel...@gmail.com (JIRA)














































Steven Crellin
 commented on  JENKINS-13554


Re: Matrix jobs does not automatically remove old artifacts for configurations















I'm also seeing this issue... very annoying. I'm spending hours every week cleaning up old build artefacts from jenkins/jobs/EveryJobName/modules/EveryModuleName/builds/*
Jenkins 1.505 on Windows 2008R2

Plugins:
Jenkins Mailer Plugin 1.4
External Monitor Job Type Plugin 1.1
LDAP Plugin 1.2
pam-auth 1.0
Ant Plugin 1.2
Javadoc Plugin 1.1
Jenkins CVS Plug-in 2.8
Hudson Support Subscription Notification Plugin 1.2
Maven 2 Project Plugin 1.505
Jenkins Artifact Deployer Plug-in 0.26
Jenkins Subversion Plug-in 1.45
Config AutoRefresh Plugin 1.0
Jenkins Workspace Cleanup Plugin 0.12
Configuration Slicing plugin 1.36
Jenkins DocLinks plugin 0.5
xUnit plugin 1.52
Jenkins Gallio plugin 1.6
Jenkins GIT client plugin 1.0.4
Jenkins Parameterized Trigger plugin 2.17
Jenkins GIT plugin 1.3.0
Green Balls 1.12
Nested View Plugin 1.9
Jenkins SSH Slaves plugin 0.22
Startup Trigger 2.3
ThinBackup 1.7.2
Jenkins Translation Assistance plugin 1.10




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 


[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-06-07 Thread jos...@azariah.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163615#comment-163615
 ] 

Joshua Kugler commented on JENKINS-13554:
-

After disabling the promoted builds plugin, and cleaning up all the abandoned 
builds, it *seems* we no longer have this issue.

> 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: matrix
>Affects Versions: current
>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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread jos...@azariah.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161992#comment-161992
 ] 

Joshua Kugler commented on JENKINS-13554:
-

Just another data point: we disabled the Promoted Builds plugin, restarted, and 
are still having the issue.

> 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: matrix
>Affects Versions: current
>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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread stibb...@java.net (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161957#comment-161957
 ] 

stibbons edited comment on JENKINS-13554 at 4/24/12 12:33 PM:
--

Here are information about my install:

Jenkins 1.460 under linux 64b

System Properties
executable-war  /usr/share/jenkins/jenkins.war
file.encoding   UTF-8
file.encoding.pkg   sun.io
file.separator  /
hudson.diyChunking  true
java.awt.graphicsenvsun.awt.X11GraphicsEnvironment
java.awt.headless   true
java.awt.printerjob sun.print.PSPrinterJob
java.class.path /usr/share/jenkins/jenkins.war
java.class.version  50.0
java.endorsed.dirs  /usr/lib/jvm/java-6-openjdk/jre/lib/endorsed
java.ext.dirs   
/usr/lib/jvm/java-6-openjdk/jre/lib/ext:/usr/java/packages/lib/ext
java.home   /usr/lib/jvm/java-6-openjdk/jre
java.io.tmpdir  /tmp
java.library.path   
/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/jni:/lib:/usr/lib
java.runtime.name   OpenJDK Runtime Environment
java.runtime.version1.6.0_23-b23
java.specification.name Java Platform API Specification
java.specification.vendor   Sun Microsystems Inc.
java.specification.version  1.6
java.vendor Sun Microsystems Inc.
java.vendor.url http://java.sun.com/
java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi
java.version1.6.0_23
java.vm.infomixed mode
java.vm.nameOpenJDK 64-Bit Server VM
java.vm.specification.name  Java Virtual Machine Specification
java.vm.specification.vendorSun Microsystems Inc.
java.vm.specification.version   1.0
java.vm.vendor  Sun Microsystems Inc.
java.vm.version 20.0-b11
javamelody.analytics-id UA-1335263-7
javamelody.http-transform-pattern   
/\d+/|/site/.+|avadoc/.+|/ws/.+|obertura/.+|estReport/.+|iolations/file/.+|/user/.+|/static/\w+/
javamelody.no-database  true
javamelody.storage-directory//home/jenkins/jenkins/monitoring
javamelody.system-actions-enabled   true
javax.accessibility.assistive_technologies  
org.GNOME.Accessibility.JavaBridge
jna.platform.library.path   
/usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator  
mail.smtp.sendpartial   true
mail.smtps.sendpartial  true
os.arch amd64
os.name Linux
os.version  3.0.0-15-generic
path.separator  :
pid 24094
sun.arch.data.model 64
sun.boot.class.path 
/usr/lib/jvm/java-6-openjdk/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-openjdk/jre/classes
sun.boot.library.path   /usr/lib/jvm/java-6-openjdk/jre/lib/amd64
sun.cpu.endian  little
sun.cpu.isalist 
sun.io.unicode.encoding UnicodeLittle
sun.java.command/usr/share/jenkins/jenkins.war 
--webroot=/var/run/jenkins/war --httpPort=8080 --ajp13Port=-1
sun.java.launcher   SUN_STANDARD
sun.jnu.encodingUTF-8
sun.management.compiler HotSpot 64-Bit Tiered Compilers
sun.os.patch.level  unknown
svnkit.http.methods Digest,Basic,NTLM,Negotiate
svnkit.ssh2.persistent  false
svnkit.symlinks false
user.countryUS
user.dir/
user.home   /home/jenkins
user.language   en
user.name   jenkins
user.timezone   Europe/Paris

NameVersion Enabled Pinned
javadoc 1.0 truefalse
ant 1.1 truefalse
token-macro 1.5.1   truefalse
maven-plugin1.460   truetrue
cvs 2.3 truetrue
doclinks0.5 truefalse
dashboard-view  2.2 truefalse
analysis-core   1.39truefalse
tasks   4.28truefalse
warnings4.0 truefalse
ci-game 1.18truefalse
subversion  1.39truetrue
viewVC  1.5 truefalse
jquery  1.0.2   truefalse
URLSCM  1.6 truefalse
project-stats-plugin0.3 truefalse
slave-status1.6 truefalse
mercurial   1.38truefalse
klaros-testmanagement   1.4 truefalse
build-timeout   1.8 truefalse
ssh 1.3 truefalse
description-setter  1.8 truefalse
scm-sync-configuration  0.0.4   truefalse
0.6 truefalse
scis-ad 1.2 truefalse
htmlpublisher   0.7 truefalse
build-pipeline-plugin   1.2.3   false   false
saferestart 0.2 truefalse
progress-bar-column-plugin  1.0 truefalse
depgraph-view   0.2 truefalse
svn-tag 1.16truefalse
validating-string-parameter 2.2 truefalse
xfpanel 1.

[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread stibb...@java.net (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161957#comment-161957
 ] 

stibbons commented on JENKINS-13554:


Here are information about install:

Jenkins 1.460

NameVersion Enabled Pinned
javadoc 1.0 truefalse
ant 1.1 truefalse
token-macro 1.5.1   truefalse
maven-plugin1.460   truetrue
cvs 2.3 truetrue
doclinks0.5 truefalse
dashboard-view  2.2 truefalse
analysis-core   1.39truefalse
tasks   4.28truefalse
warnings4.0 truefalse
ci-game 1.18truefalse
subversion  1.39truetrue
viewVC  1.5 truefalse
jquery  1.0.2   truefalse
URLSCM  1.6 truefalse
project-stats-plugin0.3 truefalse
slave-status1.6 truefalse
mercurial   1.38truefalse
klaros-testmanagement   1.4 truefalse
build-timeout   1.8 truefalse
ssh 1.3 truefalse
description-setter  1.8 truefalse
scm-sync-configuration  0.0.4   truefalse
0.6 truefalse
scis-ad 1.2 truefalse
htmlpublisher   0.7 truefalse
build-pipeline-plugin   1.2.3   false   false
saferestart 0.2 truefalse
progress-bar-column-plugin  1.0 truefalse
depgraph-view   0.2 truefalse
svn-tag 1.16truefalse
validating-string-parameter 2.2 truefalse
xfpanel 1.0.11  truefalse
sidebar-link1.6 truefalse
exclusive-execution 0.7 truefalse
cvs-tag 1.7 truefalse
promoted-builds 2.5 truefalse
release 2.2 truefalse
xvnc1.10truefalse
statusmonitor   1.3 false   false
svn-release-mgr 1.2 truefalse
measurement-plots   0.1 truefalse
timestamper 1.2.2   truefalse
jquery-ui   1.0.2   truefalse
filesystem_scm  1.20truefalse
screenshot  1.1 truefalse
jobtype-column  1.2 truefalse
keepSlaveOffline1.0 truefalse
show-build-parameters   1.0 truefalse
tmpcleaner  1.1 truefalse
nested-view 1.8 truefalse
copyartifact1.22truefalse
promoted-builds-simple  1.9 truefalse
cmakebuilder1.9 truefalse
emotional-jenkins-plugin1.1 truefalse
versionnumber   1.4.1   truefalse
vmware  0.8 truefalse
tracking-svn1.1 truefalse
girls   1.0.0   false   false
lastsuccessversioncolumn1.1 truefalse
description-column-plugin   1.3 truefalse
backup  1.6.1   truefalse
plot1.5 truefalse
scp 1.8 truefalse
systemloadaverage-monitor   1.2 truefalse
copy-to-slave   1.4 truefalse
postbuild-task  1.8 truefalse
sectioned-view  1.16truefalse
hudson-wsclean-plugin   1.0.4   truefalse
locale  1.2 truefalse
favorite1.6 truefalse
terminal1.3 truefalse
radiatorviewplugin  1.13false   false
emotional-hudson1.3 false   false
copyarchiver0.5.1   truefalse
role-strategy   1.1.2   truefalse
parameterized-trigger   2.13truefalse
email-ext   2.20truefalse
git 1.1.17  truefalse
all-changes 1.3 truefalse
ftppublisher1.2 truefalse
svnpublisher0.1 truefalse
template-project1.3 truefalse
built-on-column 1.1 truefalse
matrixtieparent 1.1 truefalse
greenballs  1.11truefalse
sloccount   1.6 truefalse
dropdown-viewstabbar-plugin 1.4 truefalse
xunit   1.43truefalse
cppunit 1.10truefalse
next-executions 1.0.4   truefalse
doxygen 0.10truefalse
rebuild 1.10truefalse
disk-usage  0.16truefalse
virtualbox  0.4.6   truefalse
jobConfigHistory1.13truefalse
extra-columns   1.3 truefalse
clone-workspace-scm 0.4 truefalse
ssh-slaves  0.21truetrue
multiple-scms   0.2 truefalse
groovy-postbuild1.6 truefalse
ui-samples-plugin   1.460   false   false
jenkinswalldisplay  0.6.9   truefalse
run-condition   0.8 truefalse
cppcheck1.7 truefalse
scripttrigger   0.16truefalse
downstream-ext  1.7 truefalse
join1.14truefalse
ws-cleanup  0.8 truefalse
groovy  1.12truefalse
downstream-buildview1.7 truefalse
job-exporter0.4 truefalse
cobertura   1.3 truefalse
testlink3.1.2   truefalse
analysis-collector  1.25truefalse
monitoring  1.36.0  truefalse
conditional-buildstep   1.0 truefalse
testng-plugin   0.32truefalse
thinBackup  1.5 truefalse
batch-task  1.15truefalse
ansicolor   0.2.1   truefalse
translatio

[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread vjura...@java.net (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161920#comment-161920
 ] 

vjuranek commented on JENKINS-13554:


I'll check it, but IIRC addition of "Delete this Build and all configuration in 
this build" only added new function to delete matrix job with all it's sub-jobs 
as "Delete this build" deletes only matrix jobs parent itself. 

> 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: matrix
>Affects Versions: current
>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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread stibb...@java.net (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161919#comment-161919
 ] 

stibbons commented on JENKINS-13554:


I'm pretty sure the discard old build perform the same action as "Delete this 
build" while it should do the same action as "Delete this build and all 
configuration in this build".

> 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: matrix
>Affects Versions: current
>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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread stibb...@java.net (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stibbons updated JENKINS-13554:
---

Affects Version/s: current
  Component/s: (was: disk-usage)

> 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: matrix
>Affects Versions: current
>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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-24 Thread stibb...@java.net (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161917#comment-161917
 ] 

stibbons commented on JENKINS-13554:


I think this has been introduced in 1.451 when the new delete button has been 
added in matrix job ("Delete this Build and all configuration in this build").

This is very annoying, since I have to manually check for disk space a remove 
the configuration build every 2 days..

> 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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-23 Thread jos...@azariah.com (JIRA)

[ 
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




[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-04-23 Thread stibb...@java.net (JIRA)
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