[JIRA] (JENKINS-55721) Amazon Ec2Plugin Enhancement Request
Title: Message Title max allan commented on JENKINS-55721 Re: Amazon Ec2Plugin Enhancement Request Can you use instance roles? Give the Jenkins EC2 master instance the role to create new instances etc... 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-36877) Can't select credentials
Title: Message Title max allan commented on JENKINS-36877 Re: Can't select credentials I'm not quite sure when, but at some point, the problem went away... I have 2 sets of credentials now, only one appears in the plugin. Try adding more credentials and see if they appear!! Maybe there is an off by one error somewhere. 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-38445) Pipeline withMaven Failed to serialize on agent
Title: Message Title max allan commented on JENKINS-38445 Re: Pipeline withMaven Failed to serialize on agent I was having a similar error message and problem with withMaven not running on either slave or master. Updated all plugins and core Jenkins from 2.21 to 2.23 and it seems to be working. The cause is unknown, I'm pretty sure it was working with the old versions of everything... 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-37356) OWASP checker can't update on slave
Title: Message Title max allan commented on JENKINS-37356 Re: OWASP checker can't update on slave This might be a more fundamental issue than the Jenkins plugin. I have the same problem with the command line app. https://groups.google.com/forum/#!topic/dependency-check/PIu-J8NfjGg 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-37356) OWASP checker can't update on slave
Title: Message Title max allan created an issue Jenkins / JENKINS-37356 OWASP checker can't update on slave Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2016/Aug/11 5:36 PM Environment: OWASP plugin 1.4.2, Jenkins 2.1.7 Priority: Minor Reporter: max allan I'm having some trouble getting the OWASP check to update the NVDs on a slave. I know you're going to say "Proxy settings" but it isn't! I can do a tcpdump and it does a 3 way handshake and then a "client hello" packet that Wireshark identifies as "SSL" and has the SNI information in. The nvd.nist.gov server then sends a RST packet back. (I can successfully do a curl as the jenkins user : curl https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-Modified.xml.gz works fine) And I can successfully download the updates on the master server. When comparing the tcpdump between the working download and the failing ones, the working one is detected as "TLSv1.2" rather than SSL. I did think it might be an old Java version issue, so removed 1.7 completely and installed 1.8. I also updated openSSL. No joy. Anyone any ideas?? Is it a bug, a misconfiguration (what config is there??) ?
[JIRA] (JENKINS-36877) Can't select credentials
Title: Message Title max allan updated an issue Jenkins / JENKINS-36877 Can't select credentials Change By: max allan Firstly the overview usage page for the plugin is out of date. (https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin) It looks like the latest version has partially implemented the credentials management in Jenkins, you don't define the credentials directly in the plugin any more . Then I can press the "Add" button while adding an AWS cloud , but after installing the plugin, only the "ssh" credential type was available. The plugin should probably add the "AWS key credentials" type.But, I go off, enable the "Jenkins provider, AWS key credentials" and come back to the AWS plugin, I can now add an AWS access key/secret. Test/Save.Seems good. BUT the drop down in the Add Cloud still doesn't let me chose the credentials I entered.I have tried the old method of setting them as environment variables in the jenkins user's .profile and restarting the plugin from the command line. Still no joy.Finally, in the Configure System, Add new cloud section, the credentials' descriptive text says "Amazon EC2 Crendentials" (spurious "n")So, I'm unable to choose the credentials set I defined and cannot use the plugin at all. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36877) Can't select credentials
Title: Message Title max allan created an issue Jenkins / JENKINS-36877 Can't select credentials Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Jul/22 1:11 PM Environment: 1.35 of plugin Jenkins 2.14 Priority: Blocker Reporter: max allan Firstly the overview page for the plugin is out of date. It looks like the latest version has partially implemented the credentials management in Jenkins, you don't define the credentials in the plugin. Then I can press the "Add" button, but after installing the plugin, only the "ssh" credential type was available. The plugin should probably add the "AWS key credentials" type. But, I go off, enable the "Jenkins provider, AWS key credentials" and come back to the AWS plugin, I can now add an AWS access key/secret. Test/Save. BUT the drop down in the Add Cloud still doesn't let me chose the credentials I entered. I have tried the old method of setting them as environment variables in the jenkins user's .profile and restarting the plugin from the command line. Still no joy. Finally, in the Configure System, Add new cloud section, the credentials' descriptive text says "Amazon EC2 Crendentials" (spurious "n") So, I'm unable to choose the credentials set I defined and cannot use the plugin at all.
