![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
build-flow, throttle-concurrents |
|
Created:
|
13/Jan/14 5:49 PM
|
|
Description:
|
Steps to reproduce:
1. Create a build-flow projectA
2. Setup projectA to allow concurrent builds, but configure throttling so only one build is allowed per node
3. Manually trigger multiple builds of projectA
-
- Notice that Jenkins chooses the same node for each build-flow build in a projectA.
I may be wrong, but it seems that Jenkins will only choose a different node if the build-flow job is for a different project.
In my case:
- projectA syncs source code to a local workspace on nodeA
- projectA orchestrates a parametrized build, passing nodeA as a parameter to ensure the build is done on the same node that the source code was sync'd on
- The build job has a throttle rule that only allows one build per node so even though two build-flow jobs are running on the same node, one build still has to wait for the other.
I like that flyweight jobs are excluded from the normal throttle rules, but it would be nice if users could create rules specifically for flyweight jobs; or some way to configure build-flow jobs to not use the same node for each job
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Michael Rose
|
|
|
|
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/groups/opt_out.
