![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
14/Apr/15 7:00 AM
|
|
Description:
|
After Jenkins version 1.607 jobs that run on the same SVN directory/repository and are throttled with using Throttle Concurrent Builds Plugin (Multi-Project Throttle Category is setup for these jobs, all are part of the same throttle category) are being executed at the same time and not queued correctly.
This leads to SVN locks (one project detects the lock, wants to clean and re-checkout SVN repository, others fail etc.).
This started happening with 1.607 and is still present in 1.609. Reverting back to 1.606 fixes the problem.
Not sure, if an update to the Throttle Concurrent Builds Plugin is needed or if this is a core issue.
|
|
Environment:
|
Jenkins 1.606 - 1.609, Throttle Concurrent Builds Plugin 1.8.4
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tadej Lasic
|
|
|
|
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.
