![]() |
|
|
|
|
Change By:
|
Trevor Baker
(30/Jan/15 6:03 PM)
|
|
Summary:
|
Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves
when necessary
|
|
Description:
|
The EC2 plugin works great for dynamically provisioning EC2
When concurrent jobs are throttled across categories new ec2 provisioned
slaves
(as needed)
are not launched
when
their label is specified under "Restrict where this project can be run," but it doesn't do anything if that label is passed in using a NodeLabel parameter
they are required
.
Note
The ec2 plugin should not detect
that
this only seems to affect
even though there may be executors available that they can not run
the
EC2 provisioning step; jobs set
job(s) due
to
run on a slave via NodeLabel parameter will happily run on provisioned-by-EC2-plugin slaves that are already around
concurrent throttling
.
These two plugins should interop as expected.
|
|
Assignee:
|
Dominik Bartholdi
|
|
Component/s:
|
throttle-concurrent-builds-plugin
|
|
Component/s:
|
nodelabelparameter-plugin
|
|
|
|
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.
