This plugin has an unfortunate known flaw - it will only spin up one executor/node per label. If you have two jobs waiting to build with the same label, it will build the first one, then kill after it's done, and then start the next one. (Instead of creating two containers/tasks in parallel) I've tried all the hacks (single build slave plugin, etc) and they no longer work.
For this reason I've decided not to use it. You're much better off using the EC2 plugin (which is very well supported), registering those nodes as build agents, and then using Jenkins' native Docker workflow with pipelines. (In essence, this means Jenkins will run docker containers on the EC2 machine) On Monday, July 18, 2016 at 12:46:41 AM UTC-4, Tez Macca wrote: > > Hi, > > I have configured the "Amazon EC2 Container Service Plugin" with a single > statically associated EC2 instance. My expectation is that multiple > slaves/containers would be started when there are multiple jobs scheduled. > However, I get the following message when the second job runs: > *Waiting for next available executor on aws-slaves-c50dc930a5d94* > Where '*aws-slaves-c50dc930a5d94'* is the node instance started by the > first job. The jobs start and execute perfectly though. > > To get multiple executors do I need to change something with: > 1. how I have configured the AWS plugin, > 2. OR the ECS cluster in AWS, > 3. OR my Jenkinsfile needs something like concurrency set in the stage? > > This also means that I am unable to run multiple parallel steps. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/341c64b3-a025-49e3-9e2a-bf165559c88d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
