[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-31197 New jobs are not creating a new container Change By: Philipp Garbe Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Nicolas De Loof assigned an issue to Jan Roehrich Jenkins / JENKINS-31197 New jobs are not creating a new container Change By: Nicolas De Loof Assignee: Nicolas De Loof Jan Roehrich Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Dima Shmakov commented on JENKINS-31197 Re: New jobs are not creating a new container In any case, it's better to use Spotinst with AWS to run all jenkins stuff on spot instances (70-80% savings ), there's Spotinst plugin for jenkins, that will spin new servers when jobs are in queue, and turn them off after some idle time. Very convenient. We'll be soon migrating to DCOS or Kubernetes, for all Docker related services and workloads, so will be no need to use ECS pools. Kubernetes is supercool , it also has jenkins plugins for dynamic slaves. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Dima Shmakov commented on JENKINS-31197 Re: New jobs are not creating a new container Joshua Noble we use 2.19 , recently upgraded the ECS plugin to 1.6 and it stopped working, so rolled back to 1.5 . for now it works ok , though I need to cleanup "used slaves" manually with a groovy script, it doesn't clean. did you set "Execute concurrent builds if necessary" ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Joshua Noble commented on JENKINS-31197 Re: New jobs are not creating a new container Dima Shmakov What version of Jenkins are you using? I tried your workaround with both the Throttle Concurrent and Single Use Slave plugins without any success. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Joshua Noble commented on JENKINS-31197 Re: New jobs are not creating a new container Any more movement on this issue? Given Docker's ephemeral nature we really should modify this plugin to fulfill the OP's request, as it also matches my own. We should be able to spin up multiple new slaves via ECS tasks for the same label. Currently only one slave can run at a time per label - that's a significant bottleneck. Would this logic be contained within this plugin's source - or within the Jenkins core? If someone could point me in the right direction, I might be able to attempt to spend a few cycles on this. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
