[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title Brian L commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames It would be really great to see a new release of this plugin. My team has seen a few issues working with the ec2-plugin, and we're hoping things will get smoother soon. On GitHub, there have been 14 commits to the master branch since the last release (August 2, 2015). One notable change (IMHO), is that the aws-java-sdk dependency has been upgraded from version 1.10.2 (used in the last release) to 1.10.26 (currently in the master branch). Can someone please comment as to when an update is expected, or if another plugin should be preferred? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Title: Message Title Brian L commented on JENKINS-22932 Re: Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I didn't have much luck with an actual patch, but in the meantime, here's the workaround I'm attempting to implement: 1. Install the Groovy plugin 2. Use this code as it's own Job : import jenkins.model.* println "The system is now going down for restart." println "Once the bug 'https://issues.jenkins-ci.org/browse/JENKINS-22932' is resolved, this job should be removed." Jenkins.instance.doSafeRestart(null); 3. Have the job triggered after any of your Windows slaves finish doing work Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Title: Message Title
Brian L edited a comment on JENKINS-22932
Re: Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
This is affecting me as well. Master: Jenkins ver. 1.638, Ubuntu 14.04.3 LTS, running JRE 1.8.0_65-b17 Slave: Windows Server 2008, connected via JNLP : { { code} Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>java -versionjava version "1.8.0_31"Java(TM) SE Runtime Environment (build 1.8.0_31-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode) {code } } Do we have a workaround? I wonder if adding some Job configuration to programmatically kill the process running {{java ... -jar "...\slave.jar"}} might work?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Title: Message Title
Brian L commented on JENKINS-22932
Re: Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
This is affecting me as well.
Master: Jenkins ver. 1.638, Ubuntu 14.04.3 LTS, running JRE 1.8.0_65-b17 Slave: Windows Server 2008, connected via JNLP :
{{Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>java -version java version "1.8.0_31" Java(TM) SE Runtime Environment (build 1.8.0_31-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)}}
Do we have a workaround? I wonder if adding some Job configuration to programmatically kill the process running java ... -jar "...\slave.jar" might work?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [ec2-plugin] (JENKINS-31641) Unclear error upon launching Windows build node
Title: Message Title Brian L created an issue Jenkins / JENKINS-31641 Unclear error upon launching Windows build node Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 19/Nov/15 2:13 AM Environment: Ubuntu 14.04.3 LTS, running the JRE 1.8.0_65-b17 and Jenkins 1.635 Priority: Minor Reporter: Brian L It would be great if this error could give better guidance as to what configuration option is missing or incorrect. Currently, I'm trying to setup my first Windows slave node and not having much luck. From the Jenkins log ( http://host/jenkins/log/all ) : Nov 19, 2015 2:02:51 AM WARNING hudson.plugins.ec2.win.WinConnection ping Failed to verify connectivity to Windows slave java.lang.IllegalArgumentException: Scheme may not be null at org.apache.http.util.Args.notNull(Args.java:48) at org.apache.http.conn.scheme.SchemeRegistry.register(SchemeRegistry.java:123) at hudson.plugins.ec2.win.winrm.WinRMClient.sendRequest(WinRMClient.java:220) at hudson.plugins.ec2.win.winrm.WinRMClient.sendRequest(WinRMClient.java:202) at hudson.plugins.ec2.win.winrm.WinRMClient.openShell(WinRMClient.java:85) at hudson.plugins.ec2.win.winrm.WinRM.ping(WinRM.java:29) at hudson.plugins.ec2.win
[JIRA] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title
Brian L edited a comment on JENKINS-31089
Re: Signature verification failed in update site 'default'
Just adding that this also affects Ubuntu 14.04.3 LTS, running the JRE 1.8.0_65-b17 and Jenkins 1.635 . The machine was configured using [Bitnami's AMI](https://aws.amazon.com/marketplace/pp/B00NNZUF3Q), but that shouldn't matter. Replacing ` {{ jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024 ` }} with ` {{ jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 512 ` }} in the file ` {{ $JRE_HOME/ / lib/securityjava.security ` }} has resolved this for me as well.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-31089) Signature verification failed in update site 'default'
Title: Message Title Brian L commented on JENKINS-31089 Re: Signature verification failed in update site 'default' Just adding that this also affects Ubuntu 14.04.3 LTS, running the JRE 1.8.0_65-b17 and Jenkins 1.635 . The machine was configured using [Bitnami's AMI](https://aws.amazon.com/marketplace/pp/B00NNZUF3Q), but that shouldn't matter. Replacing `jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024` with `jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 512` in the file `$JRE_HOME//lib/securityjava.security` has resolved this for me as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
