-
Bug
-
Resolution: Unresolved
-
Major
-
None
Hello, all
When trying on ec2 plugin, my case is that I want 2 slaves label with lable "tpr" by regular use.
In some case if there are many job request, we will launch more slaves dynamically with ec2 plugin, the cloud configuration has same label "tpr"
But we found the ec2 plugin doesn't work in this case, and job always wait on executors on slaves labeled with "tpr" even they are occupied, jenkins doesn't try to launch new slave with the cloud configuration.
Not sure it's a bug or it's by design, but it would be great if ec2 still work in this case.
[JENKINS-46044] ec2 plugin doesn't work it has same label with other slaves
Description |
Original:
Hello, all When trying on ec2 plugin, my case is that I want 2 slaves label with tpr by regular use. In some case if there are many job request, we will launch more slaves dynamically with ec2 plugin. But we found the ec2 plugin doesn't work in this case, and job always wait on executors on slaves labeled with "tpr" even they are occupied, jenkins doesn't try to launch new slave with the cloud configuration. Not sure it's a bug or it's by design, but it would be great if ec2 still work in this case. |
New:
Hello, all When trying on ec2 plugin, my case is that I want 2 slaves label with lable "tpr" by regular use. In some case if there are many job request, we will launch more slaves dynamically with ec2 plugin, the cloud configuration has same label "tpr" But we found the ec2 plugin doesn't work in this case, and job always wait on executors on slaves labeled with "tpr" even they are occupied, jenkins doesn't try to launch new slave with the cloud configuration. Not sure it's a bug or it's by design, but it would be great if ec2 still work in this case. |