[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Tobias Krönke assigned an issue to FABRIZIO MANFREDI Jenkins / JENKINS-53920 After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again Change By: Tobias Krönke Assignee: Tobias Krönke FABRIZIO MANFREDI 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Tobias Krönke resolved as Fixed Jenkins / JENKINS-53920 After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again Change By: Tobias Krönke Status: In Progress Resolved Resolution: Fixed 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Tobias Krönke commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again i think so. for us it is working again with the latest version. 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-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Tobias Krönke assigned an issue to Tobias Krönke Jenkins / JENKINS-53920 After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again Change By: Tobias Krönke Assignee: FABRIZIO MANFREDI Tobias Krönke 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-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title Tobias Krönke commented on JENKINS-54071 Re: EC2-plugin not spooling up stopped nodes Could someone confirm, this was fixed in 1.41? I made sure, I added iam:ListInstanceProfilesForRole to the master's role policy. Then I terminated the old slave (only 1 currently). Building a job now correctly spins up a new instance (cap for this AMI is set to 1). Afterwards the instance is stopped after 1 minute of idling. Then for the next build it only seems to attempt to provision another machine (which of course fails with the cap limit). see the attached ec2.log 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-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title Tobias Krönke updated an issue Jenkins / JENKINS-54071 EC2-plugin not spooling up stopped nodes Change By: Tobias Krönke Attachment: ec2.log 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.
