[JIRA] (JENKINS-48273) Self-connecting agents
Title: Message Title Andreas Lutro commented on JENKINS-48273 Re: Self-connecting agents Possibly a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-26369 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186859.1511907922000.20097.1563964440188%40Atlassian.JIRA.
[JIRA] (JENKINS-33973) Add ability to launch instance without a key pair
Title: Message Title Andreas Lutro commented on JENKINS-33973 Re: Add ability to launch instance without a key pair Related: https://issues.jenkins-ci.org/browse/JENKINS-48273 and https://issues.jenkins-ci.org/browse/JENKINS-26369 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169464.145950076.20094.1563964380212%40Atlassian.JIRA.
[JIRA] (JENKINS-26369) Allow manual slave launch instead of SSH for on-demand instances
Title: Message Title Andreas Lutro edited a comment on JENKINS-26369 Re: Allow manual slave launch instead of SSH for on-demand instances I'd also like to see this happening. I've pre-configured the AMI which the EC2 plugin uses so that the Jenkins agent gets downloaded and installed on boot, kind of as described here: [https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-ConfigureAMIforSpotSupport]However, Jenkins still insists on SSHing to the instance, even though it's not necessary. Yes, this is about the initial launch. This ticket is possibly a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-48273 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160033.1420821935000.20091.1563964320173%40Atlassian.JIRA.
[JIRA] (JENKINS-26369) Allow manual slave launch instead of SSH for on-demand instances
Title: Message Title Andreas Lutro commented on JENKINS-26369 Re: Allow manual slave launch instead of SSH for on-demand instances I'd also like to see this happening. I've pre-configured the AMI which the EC2 plugin uses so that the Jenkins agent gets downloaded and installed on boot, kind of as described here: https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-ConfigureAMIforSpotSupport However, Jenkins still insists on SSHing to the instance, even though it's not necessary. Yes, this is about the initial launch. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160033.1420821935000.20077.1563963780496%40Atlassian.JIRA.
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title Andreas Lutro commented on JENKINS-44609 Re: Docker inspect failing on named multi-stage builds If you want to submit a "better" PR then don't let me stop you, but I'd rather have a working plugin with workarounds than a non-working one until someone (whoever that is) submits a "proper" solution. That being said, is this plugin even being maintained? Am I wasting my time commenting here and making a PR? 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-44609) Docker inspect failing on named multi-stage builds
Title: Message Title Andreas Lutro commented on JENKINS-44609 Re: Docker inspect failing on named multi-stage builds I'm not an experienced java developer but this has been annoying me for way too long. I've opened a PR here with more fixes for this issue, but could use some guidance. https://github.com/jenkinsci/docker-workflow-plugin/pull/149 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
