![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Oleg Nenashev
|
|
Components:
|
throttle-concurrent-builds-plugin |
|
Created:
|
02/Apr/15 5:40 AM
|
|
Description:
|
After upgrading to 1.607 we noticed the throttle plugin doesn't always prevent jobs from running in parallel as expected.
Steps to reproduce:
1. Create a throttle category with global limit 1, per-node limit 1.
2. Create 3 jobs using the category, restricted to a node with two executors, sleep 60 as a build step.
3. Request builds of all 3 jobs.
What should happen:
4. Jobs run in sequence; 1 then 2 then 3.
What actually happens:
5. Job 1 starts building, jobs 2 and 3 wait in queue (OK).
6. After job 1 finishes, both job 2 and 3 start running (not OK).
Plugin version is 1.8.4. Issue does not appear in Jenkins 1.606 with the same version of the plugin. Issue is reproducible on a fresh install.
We were forced to downgrade back to 1.606 as a workaround (which is unfortunately not trivial due to JENKINS-27700).
|
|
Environment:
|
Jenkins 1.607
Throttle concurrent builds plugin 1.8.4
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Tomasz Śniatowski
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
