![]() |
|
|
Issue Type:
|
Bug
|
Assignee:
|
Unassigned |
Components:
|
core |
Created:
|
24/Jul/14 7:23 AM
|
Description:
|
Despite the fact that Discard Old Builds is enabled and Max # of builds to keep is set to 10, there are many old builds remain in <job_name>/builds directory.
It should be noted that at the same time those not deleted builds are not visible via web GUI of Jenkins.
This problem arise for jobs that have Execute concurrent builds if necessary option enabled.
How to reproduce
The job (let's call it jobA), beside Discard Old Builds, should have Execute concurrent builds if necessary option enabled.
Make some of the nodes busy by running another job (e.g.: jobC) on them.
Launch jobA a few times via Jenkins web interface. The number of running jobA should be bigger than number set in Max # of builds to keep.
When jobC completes, all instances of running jobA will be able to complete.
Check jobA/builds/ directory at Jenkins, there are not discarded builds.
Version of Jenkins this bug is occurring
How we are running Jenkins
Environment we are using
|
Environment:
|
Red Hat Enterprise Linux Server
java version "1.7.0_60"
|
Project:
|
Jenkins
|
Labels:
|
jenkins
|
Priority:
|
Major
|
Reporter:
|
Maxim Strygin
|
|
|
|
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/d/optout.