-
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.
I have this problem too, we created a single jenkins system to be used by our entire company, but because of this queue build up on common labels like "ubuntu" and "windows" there's an exponential queue time of waiting for executors and eventually creating a new instance. Was hoping the One-Shot Executor Plugin would fix this, however that only supplies an API to be used by other plugins and the Amazon EC2 plugin doesn't implement this API. Working on creating a custom plugin to tie these 2 community plugins together.