[JIRA] (JENKINS-13039) Max # of builds to keep not deleting old builds
Thomas B commented on JENKINS-13039 Max # of builds to keep not deleting old builds Same issue here too. In addition job.logRotate() encounters "delete" exceptions on a few % of my build (it manages to delete the build but think it's still here ...) and since I've stacked 800+ builds (instead of 4) it's pretty enoying Using version Jenkins ver. 1.489 on Linux 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
[JIRA] (JENKINS-13039) Max # of builds to keep not deleting old builds
[
https://issues.jenkins-ci.org/browse/JENKINS-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161819#comment-161819
]
Yves DM commented on JENKINS-13039:
---
Encountering same issue.
Using version 1.459 of jenkins on windows 2008 r2 plateform.
Max # of builds to keep not deleting old builds
---
Key: JENKINS-13039
URL: https://issues.jenkins-ci.org/browse/JENKINS-13039
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: allenservedio
Setting the Max # of builds to keep for a job does not cause old builds to
be discarded. I set this as Major as this will lead to the build system dying
after running out of disk space.
I have found a work around here:
http://groups.google.com/group/jenkinsci-users/browse_thread/thread/5573bee99bc2c42d
I created a job in my Jenkins instance to run the following groovy script (as
a system groovy script - not sure if that matters...) - this forces the old
builds to be discarded per what I have defined in the config:
{code}
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
{code}
--
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-13039) Max # of builds to keep not deleting old builds
allenservedio created JENKINS-13039:
---
Summary: Max # of builds to keep not deleting old builds
Key: JENKINS-13039
URL: https://issues.jenkins-ci.org/browse/JENKINS-13039
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: allenservedio
Setting the Max # of builds to keep for a job does not cause old builds to be
discarded. I set this as Major as this will lead to the build system dying
after running out of disk space.
I have found a work around here:
http://groups.google.com/group/jenkinsci-users/browse_thread/thread/5573bee99bc2c42d
I created a job in my Jenkins instance to run the following groovy script (as a
system groovy script - not sure if that matters...) - this forces the old
builds to be discarded per what I have defined in the config:
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
--
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-13039) Max # of builds to keep not deleting old builds
[
https://issues.jenkins-ci.org/browse/JENKINS-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
allenservedio updated JENKINS-13039:
Description:
Setting the Max # of builds to keep for a job does not cause old builds to be
discarded. I set this as Major as this will lead to the build system dying
after running out of disk space.
I have found a work around here:
http://groups.google.com/group/jenkinsci-users/browse_thread/thread/5573bee99bc2c42d
I created a job in my Jenkins instance to run the following groovy script (as a
system groovy script - not sure if that matters...) - this forces the old
builds to be discarded per what I have defined in the config:
{code}
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
{code}
was:
Setting the Max # of builds to keep for a job does not cause old builds to be
discarded. I set this as Major as this will lead to the build system dying
after running out of disk space.
I have found a work around here:
http://groups.google.com/group/jenkinsci-users/browse_thread/thread/5573bee99bc2c42d
I created a job in my Jenkins instance to run the following groovy script (as a
system groovy script - not sure if that matters...) - this forces the old
builds to be discarded per what I have defined in the config:
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
Max # of builds to keep not deleting old builds
---
Key: JENKINS-13039
URL: https://issues.jenkins-ci.org/browse/JENKINS-13039
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: allenservedio
Setting the Max # of builds to keep for a job does not cause old builds to
be discarded. I set this as Major as this will lead to the build system dying
after running out of disk space.
I have found a work around here:
http://groups.google.com/group/jenkinsci-users/browse_thread/thread/5573bee99bc2c42d
I created a job in my Jenkins instance to run the following groovy script (as
a system groovy script - not sure if that matters...) - this forces the old
builds to be discarded per what I have defined in the config:
{code}
import hudson.model.*
for(job in Hudson.instance.items) {
job.logRotate()
}
{code}
--
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
