![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Oleg Nenashev
|
|
Components:
|
throttle-concurrent-builds-plugin |
|
Created:
|
24/Apr/15 11:45 AM
|
|
Description:
|
Many times when someone manually schedules a job to execute it will end up executing multiple builds of jobs that are in the same Category (limited to 1 per node and 1 in total) concurrently.
I have a single Jenkins server, no slaves, and a setup like this:
Job A - triggered by Git updates, part of category X
Job B - triggered by A on success, part of category X
Job C,D - triggered by A on success, part of category Y
Job E - triggered by timer, part of category X
When Git updates trigger Job A and while A is running I manually schedule Job E to run (both are part of category X that allows only 1 concurrent build), then Job E waits for A to finish as expected. But when A is done successfully then Jobs B, C, D and E start all at the same time.
Problem is the B and E are part of category X as well so they should never run at the same time.
I didn't see this before recently upgrading all plugins and Jenkins.
|
|
Environment:
|
Jenkins 1.608
Throttle Concurrent Builds Plugin 1.8.4
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Andrei Costescu
|
|
|
|
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.
