New jobs are not creating a new container

XMLWordPrintable

    • Type: Bug
    • Resolution: Done
    • Priority: Minor
    • Component/s: amazon-ecs-plugin
    • None

      When I use the amazon-ecs-plugin and have multiple jobs that use the same slave label they will all attempt to use the same container instead of creating a new container for each job. Since the container only has a single executor these jobs will wait in the queue and only run once the other job is complete. My understanding is that each job should launch a new container and not reuse a container that was already launched. If I have multiple clouds defined in Manage Jenkins and I run a single job for each at the same time they will each create a separate container. It seems that only when I am using the same cloud the container will be reused until the point that it is removed (which seems to be 2 - 3 minutes after the job completes instead of immediately after the job is done.

            Assignee:
            Jan Roehrich
            Reporter:
            Dave Opfer
            Votes:
            5 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: