Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Container not spawned if dumb slave also matches #50

Closed
thomassuckow opened this issue Jul 3, 2014 · 1 comment
Closed

Container not spawned if dumb slave also matches #50

thomassuckow opened this issue Jul 3, 2014 · 1 comment

Comments

@thomassuckow
Copy link
Contributor

I am working to migrate some VM's to using docker. I am finding that if both a dumb slave and a docker image match the label conditions for the build, no docker containers are spun up despite there being a backlog of jobs.
@thomassuckow thomassuckow changed the title Container not spawned if non docker slave also matches Container not spawned if dumb slave also matches Jul 3, 2014
@thomassuckow thomassuckow mentioned this issue Jul 7, 2014
Closed
@thomassuckow
Copy link
Contributor Author

After more testing, this seems to be Jenkins taking a while to spin up Cloud slaves if a dumb slave exists. I suspect it may be related to if there is a time estimate for the job.

@djl197 djl197 mentioned this issue Oct 14, 2014
Closed
@skornehl skornehl mentioned this issue Oct 15, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thomassuckow