-
Bug
-
Resolution: Unresolved
-
Major
-
None
When concurrent jobs are throttled across categories new ec2 provisioned slaves are not launched when they are required. The ec2 plugin should detect that even though there may be executors available that they can not run the job(s) due to concurrent throttling. These two plugins should interop as expected.
- is related to
-
JENKINS-25963 Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves
-
- Open
-
[JENKINS-26716] Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary
Component/s | New: throttle-concurrent-builds-plugin [ 15745 ] | |
Component/s | Original: nodelabelparameter-plugin [ 15873 ] | |
Assignee | Original: Dominik Bartholdi [ domi ] | |
Description | Original: The EC2 plugin works great for dynamically provisioning EC2 slaves (as needed) 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. Note that this only seems to affect the EC2 provisioning step; jobs set to run on a slave via NodeLabel parameter will happily run on provisioned-by-EC2-plugin slaves that are already around. | New: When concurrent jobs are throttled across categories new ec2 provisioned slaves are not launched when they are required. The ec2 plugin should not detect that even though there may be executors available that they can not run the job(s) due to concurrent throttling. These two plugins should interop as expected. |
Summary | Original: Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves | New: Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary |
Link | New: This issue is related to JENKINS-25963 [ JENKINS-25963 ] |
Summary | Original: Jobs thottled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary | New: Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary |
Description | Original: When concurrent jobs are throttled across categories new ec2 provisioned slaves are not launched when they are required. The ec2 plugin should not detect that even though there may be executors available that they can not run the job(s) due to concurrent throttling. These two plugins should interop as expected. | New: When concurrent jobs are throttled across categories new ec2 provisioned slaves are not launched when they are required. The ec2 plugin should detect that even though there may be executors available that they can not run the job(s) due to concurrent throttling. These two plugins should interop as expected. |
Workflow | Original: JNJira [ 160792 ] | New: JNJira + In-Review [ 180490 ] |
Comment | [ Has anyone been looking on this issue? ] |
Very similar to JENKINS-25963.