-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
-
SUSE Linux Enterprise 12 SP1
jdk1.8.0_60
Jenkins ver. 1.635
apache tomcat 7.0.65
docker-plugin 0.16.0
Hi folks,
Setup a Jenkins with docker-plugin. Add a classical (non-dockered) slave to the machine.
Create a docker configuration, setting the Container Cap to 1 (i.e. only one single container may be run). Create a template, add a label to it. Create two small jobs (simply doing nothing) and assign them to the label. Start the jobs.
Observed behaviour: No docker slave is started; they are queued.
Expected behaviour: At least one docker slave is started, processing the first one of the two jobs.
Adjust the Container Cap to 2.
Observed behaviour: a docker slave is started.
If you repeat the entire setup above, leaving out the classical slave, you will notice that also with Container Cap of 1 the docker slave is started.
(similar to JENKINS-26388)
[JENKINS-36920] Docker: Standard slaves also counted into container cap
Workflow | Original: JNJira [ 173674 ] | New: JNJira + In-Review [ 185278 ] |
Assignee | Original: magnayn [ magnayn ] | New: Nico Schmoigl [ eagle_rainbow ] |
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |