[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila closed an issue as Cannot Reproduce Jenkins / JENKINS-57767 Remote call failed Change By: John Zila Status: Open Closed Resolution: Cannot Reproduce 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.199714.1559241868000.8720.1561488120755%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila commented on JENKINS-57767 Re: Remote call failed This seems to not be happening any more. I'm going to close the issue. 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.199714.1559241868000.8718.1561488060483%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila commented on JENKINS-57767 Re: Remote call failed Ping. This is making Jenkins unusable. 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.199714.1559241868000.19920.1559585880093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-57767
Remote call failed
Change By:
John Zila
Builds are randomly failing when assigned to some linux agents. Those agents are part of a fleet that behaves identically to whose other instances that work. Usually disconnecting then reconnecting to the instance fixes the problem. The builds that experience this issue fail pretty much right away.{noformat}java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)Caused: hudson.remoting.RemotingSystemException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.fetch(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:315) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.lang.ClassLoader.defineClass(ClassLoader.java:642) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:383) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.getDeclaredMethod(Class.java:2128) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1629) at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:79) at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:520) at java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:494) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.(ObjectStreamClass.java:494) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:391) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:681) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1885) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2287) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2211) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2069) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2287) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:2211) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2069) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573) at java.io.ObjectInputStream.re
[JIRA] (JENKINS-57767) Remote call failed
Title: Message Title John Zila created an issue Jenkins / JENKINS-57767 Remote call failed Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-05-30 18:44 Priority: Critical Reporter: John Zila Builds are randomly failing when assigned to some linux agents. Those agents are part of a fleet that behaves identically to other instances that work. Usually disconnecting then reconnecting to the instance fixes the problem. The builds that experience this issue fail pretty much right away. java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286) Caused: hudson.remoting.RemotingSystemException at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:299) at com.sun.proxy.$Proxy5.fetch(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:315) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at java.lang.ClassLoader.defineClass(ClassLoader.java:642) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:383) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.getDeclaredMethod(Class.java:2128) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1629) at java.io.ObjectStreamClass.acce
[JIRA] (JENKINS-48696) When an offline node comes online, pending jobs don't get assigned to it
Title: Message Title John Zila commented on JENKINS-48696 Re: When an offline node comes online, pending jobs don't get assigned to it No, it seems to be fine now, thanks. 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.187380.1513974343000.619.1557853920168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Any news here? I'm having to continue holding back my ssh-slaves plugin. 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila updated an issue Jenkins / JENKINS-53468 Since 1.27 update Channel is closing or has closed down Change By: John Zila Attachment: jenkins_thread_dump.txt 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down OK I upgraded to 1.29.1 since the trilead-api fixes, and I've applied the credentials workaround. This issue is still happening, where nodes randomly disconnect during a build. I've run a thread dump but it isn't helpful since it only shows what is running as of the newest connection to the agent machine. java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) Also: Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on i-0f47993940c6bd3da failed. The channel is closing down or has closed down Thread dump for that instance: jenkins_thread_dump.txt 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.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Gabriel Lavoie it seems that they intend on switching from `trilead-ssh2` to `trilead-api`–will you need to implement this change there too? 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I'm trying to test this but breaking changes keep stacking up for me: https://issues.jenkins-ci.org/browse/JENKINS-54686. I've disabled credentials tracking but I'll need to manually load 1.28.1 or wait for a version of SSH Slaves that has trilead-ssh2 restored. 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title
John Zila commented on JENKINS-54686
Re: Use trilead-api plugin instead trilead-ssh2 from core
SSHLauncher{host='10.0.0.21', port=22, credentialsId='b6a4fe2c-9ba5-4052-b91c-7a15e913df37', jvmOptions='-Xmx8192m', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.ManuallyTrustedKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=false}
[11/20/18 00:29:56] [SSH] Opening SSH connection to 10.0.0.21:22.
[11/20/18 00:29:57] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.
ERROR: Unexpected error in launching a agent. This is probably a bug in Jenkins.
java.lang.NoClassDefFoundError: com/trilead/ssh2/Connection
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPasswordAuthenticator$Factory.supports(TrileadSSHPasswordAuthenticator.java:194)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPasswordAuthenticator$Factory.newInstance(TrileadSSHPasswordAuthenticator.java:181)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:216)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:170)
at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1213)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:846)
at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[11/20/18 00:29:57] Launch failed - cleaning up connection
[11/20/18 00:29:57] [SSH] Connection closed.
Add Comment
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title John Zila commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core FYI this breaks the ec2-fleet plugin. 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Did you want a master thread dump? For obvious reasons, it'll be difficult to get an agent dump. Re: the issue, it happens quite sporadically–I haven't noticed a correlation between the number of agents and the probability of the issue. Frankly it seems to happen almost every time a node initially attempts to start up. I changed the retry settings to keep trying again, but those seem to be ignored. 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down And this: [11/16/18 20:42:53] [SSH] Opening SSH connection to 10.0.2.84:22. ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down And this, on Windows nodes (usually 2-3 relaunches makes it work): [11/16/18 20:42:35] [SSH] Checking java version of java [11/16/18 20:42:51] [SSH] java -version returned 1.8.0_171. [11/16/18 20:42:51] [SSH] Starting sftp client. [11/16/18 20:42:52] [SSH] Copying latest slave.jar... [11/16/18 20:42:53] [SSH] Copied 776,717 bytes. Expanded the channel window size to 4MB [11/16/18 20:42:53] [SSH] Starting slave process: cd "c:\Jenkins" && java -Xmx8192m -jar slave.jar ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:883) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) java.io.IOException: java.io.InterruptedIOException at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:1120) at hudson.plugins.sshslaves.SSHLauncher.access$500(SSHLauncher.java:148) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:845) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:820) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.io.InterruptedIOException at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:938) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:409) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:356) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:431) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:1110) ... 7 more
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I get this a bunch: ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:883) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Re-launching the node almost always fixes it, but the plugin should be doing that automatically. Instead, I get nodes that fail to launch and then engineers complaining that CI is broken. I have to manually relaunch nodes dozens of times a day. Would be nice if the SSH Slaves Plugin retry settings worked. 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down HTML Publisher plugin,1.17 Credentials Plugin,2.1.18 Pipeline: Input Step,2.8 Jackson 2 API Plugin,2.9.7.1 Pipeline,2.6 Bitbucket Pipeline for Blue Ocean,1.9.0 Blue Ocean Core JS,1.9.0 Design Language,1.9.0 OWASP Markup Formatter Plugin,1.5 Maven Integration plugin,3.1.2 External Monitor Job Type Plugin,1.7 Pub-Sub "light" Bus,1.12 Pipeline: Declarative Agent API,1.1.1 Pipeline: Declarative Extension Points API,1.3.2 Multiple SCMs plugin,0.6 GitHub Pull Request Builder,1.42.0 Server Sent Events (SSE) Gateway Plugin,1.16 Web for Blue Ocean,1.9.0 Pipeline: Shared Groovy Libraries,2.12 Docker Pipeline,1.17 Common API for Blue Ocean,1.9.0 HSTS Filter Plugin,1.0 Folders Plugin,6.6 SCM API Plugin,2.3.0 AnsiColor,0.6.0 Command Agent Launcher Plugin,1.2 Events API for Blue Ocean,1.9.0 Structs Plugin,1.17 Pipeline: Nodes and Processes,2.26 Docker Commons Plugin,1.13 Pipeline Graph Analysis Plugin,1.9 Email Extension Plugin,2.63 Pipeline: Milestone Step,1.3.1 Lockable Resources plugin,2.3 Display URL for Blue Ocean,2.2.0 Pipeline: Build Step,2.7 Git client plugin,2.7.3 Variant Plugin,1.1 Config API for Blue Ocean,1.9.0 Mercurial plugin,2.4 Bitbucket Branch Source Plugin,2.2.14 MapDB API Plugin,1.0.9.0 Pipeline: API,2.32 GitHub Pipeline for Blue Ocean,1.9.0 Workspace Cleanup Plugin,0.36 JUnit Plugin,1.26.1 GitHub Authentication plugin,0.29 Pipeline SCM API for Blue Ocean,1.9.0 Green Balls,1.15 Pipeline: REST API Plugin,2.10 Pipeline: Basic Steps,2.12 Build Timeout,1.19 Run Condition Plugin,1.2 Matrix Authorization Strategy Plugin,2.3 SSH Credentials Plugin,1.14 Plain Credentials Plugin,1.4 Metrics Plugin,4.0.2.2 Pipeline: Groovy,2.60 Credentials Binding Plugin,1.17 Pipeline: SCM Step,2.7 Rebuilder,1.29 HTTP Request Plugin,1.8.22 Pipeline: GitHub Groovy Libraries,1.0 PAM Authentication plugin,1.4 REST Implementation for Blue Ocean,1.9.0 Display URL API,2.2.0 Pipeline: Declarative,1.3.2 Pipeline: Model API,1.3.2 Port Allocator Plug-in,1.8 Durable Task Plugin,1.28 bouncycastle API Plugin,2.17 Slack Notification Plugin,2.3 GIT server Plugin,1.7 Blue Ocean,1.9.0 JSch dependency plugin,0.1.54.2 Node Iterator API Plugin,1.5.0 JIRA Integration for Blue Ocean,1.9.0 i18n for Blue Ocean,1.9.0 Git plugin,3.9.1 Dashboard for Blue Ocean,1.9.0 Role-based Authorization Strategy,2.9.0 Matrix Project Plugin,1.13 Autofavorite for Blue Ocean,1.2.2 Pipeline Remote Loader Plugin,1.4 Conditional BuildStep,1.3.6 Pipeline: Stage View Plugin,2.10 promoted builds plugin,3.2 Blue Ocean Pipeline Editor,1.9.0 Resource Disposer Plugin,0.12 Copy Artifact Plugin,1.41 _javascript_ GUI Lib: Moment.js bundle plugin,1.1.1 Git Pipeline for Blue Ocean,1.9.0 JIRA plugin,3.0.5 EC2 Fleet Jenkins Plugin,1.1.8-SNAPSHOT (private-cd808d0d-jzila) Pipeline: Job,2.29 Script Security Plugin,1.48 _javascript_ GUI Lib: Handlebars bundle plugin,1.1.1 REST API for Blue Ocean,1.9.0 Mask Passwords Plugin,2.12.0 Windows Slaves Plugin,1.3.1 Favorite,2.3.2 Pipeline: Stage Tags Metadata,1.3.2 Timestamper,1.8.10 Self-Organizing Swarm Plug-in Modules,3.14 Subversion Plug-in,2.12.1 GitHub Branch Source Plugin,2.4.1 LDAP Plugin,1.20 Pipeline: AWS Steps,1.33 SSH Slaves plugin,1.26 GitHub plugin,1.29.3 Monitoring,1.74.0 JWT for Blue Ocean,1.9.0 SSH Agent Plugin,1.17 Xvfb plugin,1.1.4-beta-1 Icon Shim Plugin,2.0.3 Authentication Tokens API Plugin,1.3 Token Macro Plugin,2.5 Apache HttpComponents Client 4.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title
John Zila edited a comment on JENKINS-53468
Re: Since 1.27 update Channel is closing or has closed down
FYI, things have been deteriorating badly. Nodes are now disconnecting even on 1. 27 26 for no reason. I tried to upgrade to 1.28.1, but then this terrible bug reared its head, making Jenkins completely unusable. I've had to revert back to 1. 27 26 to get back to a "just pretty bad" state.{noformat}Remoting version: 3.27This is a Unix agentEvacuated stdoutAgent successfully connected and onlineNov 16, 2018 5:18:27 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Nov 16, 2018 5:18:29 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/Nov 16, 2018 5:19:38 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ERROR: Connection terminatedjava.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)ERROR: Socket connection to SSH server was lostjava.net.SocketTimeoutException: The connect timeout expired at com.trilead.ssh2.Connection$1.run(Connection.java:762) at com.trilead.ssh2.util.TimeoutService$TimeoutThread.run(TimeoutService.java:91)Slave JVM has not reported exit code before the socket was lost[11/16/18 17:20:40] [SSH] Connection closed. {noformat}
Add Comment
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down FYI, things have been deteriorating badly. Nodes are now disconnecting even on 1.27 for no reason. I tried to upgrade to 1.28.1, but then this terrible bug reared its head, making Jenkins completely unusable. I've had to revert back to 1.27 to get back to a "just pretty bad" state. Remoting version: 3.27 This is a Unix agent Evacuated stdout Agent successfully connected and online Nov 16, 2018 5:18:27 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Nov 16, 2018 5:18:29 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Nov 16, 2018 5:19:38 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) ERROR: Socket connection to SSH server was lost java.net.SocketTimeoutException: The connect timeout expired at com.trilead.ssh2.Connection$1.run(Connection.java:762) at com.trilead.ssh2.util.TimeoutService$TimeoutThread.run(TimeoutService.java:91) Slave JVM has not reported exit code before the socket was lost [11/16/18 17:20:40] [SSH] Connection closed. Add Comment
[JIRA] (JENKINS-48848) Discover permissions check doesn't work
Title: Message Title John Zila commented on JENKINS-48848 Re: Discover permissions check doesn't work Thank you! 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-48848) Discover permissions check doesn't work
Title: Message Title John Zila commented on JENKINS-48848 Re: Discover permissions check doesn't work Yeah that makes sense. It has several problems, however: 1. It's difficult to discover what is happening. It seems like it shouldn't build, but instead it builds? And it's not easy to determine whether it's building from the merge target's Jenkinsfile or the branch one. 2. Jenkinsfiles are hardly the only security risk for forked builds. Just echoing an environment variable from a modified source file can be hugely damaging, potentially revealing secrets. Not to mention the ability to curl out and/or execute arbitrary code as the jenkins user on a build machine. 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down config_linux.xml 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila updated an issue Jenkins / JENKINS-53468 Since 1.27 update Channel is closing or has closed down Change By: John Zila Attachment: config_linux.xml 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Oops I gave you the config for one of our Windows agents. Let me attach the config for one of our linux agents. 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila updated an issue Jenkins / JENKINS-53468 Since 1.27 update Channel is closing or has closed down Change By: John Zila Attachment: config.xml 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Which Jenkins core version do you use? Jenkins 2.141 Which OS do you use on your SSH agents? Debian Jessie. admin@ip-10-0-0-211:~$ uname -a Linux ip-10-0-0-211 4.9.0-0.bpo.6-amd64 #1 SMP Debian 4.9.88-1+deb9u1~bpo8+1 (2018-05-13) x86_64 GNU/Linux Which OpenSSH version do you have installed on your SSH agents? admin@ip-10-0-0-211:~$ ssh -V OpenSSH_6.7p1 Debian-5+deb8u4, OpenSSL 1.0.1t 3 May 2016 Do it happen only on the SSH agents? yes Do it happen on all SSH agents or only on a few? Is there something in common between those SSH agents? randomly, most of them Are your SSH agents static or provisioned by a cloud plugin (k8s, Mesos, Docker, EC2, Azure, ...)? EC2 spot fleet plugin Could you attach the agent connection log (JENKINS_URL/computer/NODENAME/log)? No, because I'd have to switch my cluster to use the broken plugin Could you attach the logs inside the remoting folder (see https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md#remoting-work-directory)? No, as above I'd have to switch my cluster to use the broken plugin Could you attach the agent configuration (JENKINS_URL/computer/NODENAME/config.xml) file? attached config.xml Do you see if it happens always with the same job or type of job? any job Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-53468
Since 1.27 update Channel is closing or has closed down
Change By:
John Zila
We are getting crashes of the form:{noformat} java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) at java.io.ObjectInputStream.(ObjectInputStream.java:357) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on i-0893cee59e342e5da failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948)...{noformat}Ever since our update to SSH Slaves 1.27 (we are now at 1.28.1). We're attempting to manually restore 1.26 to work around this.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila created an issue Jenkins / JENKINS-53468 Since 1.27 update Channel is closing or has closed down Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2018-09-07 15:49 Priority: Critical Reporter: John Zila 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-52965) Putting Jenkins in Shutdown mode prevents any builds from completing
Title: Message Title John Zila updated an issue Jenkins / JENKINS-52965 Putting Jenkins in Shutdown mode prevents any builds from completing Change By: John Zila I'd expect Shutdown mode to prevent _new_ builds from starting (including triggered downstream builds), but in fact once existing builds complete, they just hang once all the tasks have completed.Canceling shutdown mode doesn't un-hang the builds. FWIW this happens on builds triggered by an upstream build using the `build` step. It's possible that it won't repro for builds that don't have any relationship to upstream/downstream builds. 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.
[JIRA] (JENKINS-52965) Putting Jenkins in Shutdown mode prevents any builds from completing
Title: Message Title John Zila updated an issue Jenkins / JENKINS-52965 Putting Jenkins in Shutdown mode prevents any builds from completing Change By: John Zila I'd expect Shutdown mode to prevent _new_ builds from starting (including triggered downstream builds), but in fact once existing builds complete, they just hang once all the tasks have completed. Canceling shutdown mode doesn't un-hang the builds. 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.
[JIRA] (JENKINS-52965) Putting Jenkins in Shutdown mode prevents any builds from completing
Title: Message Title John Zila created an issue Jenkins / JENKINS-52965 Putting Jenkins in Shutdown mode prevents any builds from completing Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-08-09 18:57 Priority: Major Reporter: John Zila I'd expect Shutdown mode to prevent new builds from starting (including triggered downstream builds), but in fact once existing builds complete, they just hang once all the tasks have completed. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-52924
Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Change By:
John Zila
To connect my Windows agent machines, I essentially followed this guide (modified to handle auto-scaling spot fleets via the ec2-fleet-plugin): [ https:// support go .cloudbees.com/ hc docs / en cloudbees - us documentation / articles/222978868 admin - How-to-Connect-to-Remote-SSH-Slaves-] cje/agents/#_configuring_windows_agents Until 1.22, this worked great. Since 1.23, I now get this:{noformat}[client\go] Running shell scriptps: unknown option -- oTry `ps --help' for more information.+ go list ./...+ grep -v github.com/keybase/client/go/bind+ xargs go vetwrapper script does not seem to be touching the log file in c:\Jenkins\workspace/client/master/6615\go/src/github.com/keybase/client\go@tmp\durable-8945eeb6(JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) {noformat}The failing line of my Jenkinsfile is here: [https://github.com/keybase/client/blob/aa1fc347042cafba8cf8f48a40bed59e8bce60dd/Jenkinsfile#L309]I believe this has something to do with the fix to the infinite log problem in JENKINS-37575.In the meantime, I've reverted to 1.22, and it's working again.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title
John Zila updated an issue
Jenkins / JENKINS-52924
Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Change By:
John Zila
To connect my Windows agent machines, I essentially followed this guide (modified to handle auto-scaling spot fleets via the ec2-fleet-plugin): [https://support.cloudbees.com/hc/en-us/articles/222978868-How-to-Connect-to-Remote-SSH-Slaves-]Until 1.22, this worked great. Since 1.23, I now get this:{noformat}[client\go] Running shell scriptps: unknown option -- oTry `ps --help' for more information.+ go list ./...+ grep -v github.com/keybase/client/go/bind+ xargs go vetwrapper script does not seem to be touching the log file in c:\Jenkins\workspace/client/master/6615\go/src/github.com/keybase/client\go@tmp\durable-8945eeb6(JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) {noformat}The failing line of my Jenkinsfile is here: [https://github.com/keybase/client/blob/aa1fc347042cafba8cf8f48a40bed59e8bce60dd/Jenkinsfile#L309]I believe this has something to do with the fix to the infinite log problem in JENKINS-37575. In the meantime, I've reverted to 1.22, and it's working again.
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 "Je
[JIRA] (JENKINS-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title John Zila created an issue Jenkins / JENKINS-52924 Durable Task 1.23 broke bash scripting on Windows agents via Cygwin Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-08-07 20:11 Priority: Major Reporter: John Zila To connect my Windows agent machines, I essentially followed this guide (modified to handle auto-scaling spot fleets via the ec2-fleet-plugin): https://support.cloudbees.com/hc/en-us/articles/222978868-How-to-Connect-to-Remote-SSH-Slaves- Until 1.22, this worked great. Since 1.23, I now get this: [client\go] Running shell script ps: unknown option -- o Try `ps --help' for more information. + go list ./... + grep -v github.com/keybase/client/go/bind + xargs go vet wrapper script does not seem to be touching the log file in c:\Jenkins\workspace/client/master/6615\go/src/github.com/keybase/client\go@tmp\durable-8945eeb6 (JENKINS-48300: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) The failing line of my Jenkinsfile is here: https://github.com/keybase/client/blob/aa1fc347042cafba8cf8f48a40bed59e8bce60dd/Jenkinsfile#L309 I believe this has something to do with the fix to the infinite log problem in JENKINS-37575.
[JIRA] (JENKINS-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title John Zila commented on JENKINS-37575 Re: Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Any progress on this? We just started seeing this again yesterday, with multi-GB logs and interminable builds. 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title John Zila commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent FWIW a workaround is to switch the Host Key Verification Strategy to "Manually trusted key Verification Strategy". According to the description, this automatically verifies the key on first-time connections, and subsequently requires the key to match. That is exactly what I need because we use dynamically created hosts via the EC2 Spot Fleet plugin. 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title John Zila commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent It seems like there's a legitimate bug here, where the SSH Slave Plugin SSH client doesn't report which host key types it supports. My hosts all have ssh-rsa and ecdsa-sha2-nistp256 host keys, but because the client doesn't tell the host which one it wants, the host responds only with the ecdsa-sha2-nistp266 key. This causes the plugin to fail to connect. 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title
John Zila edited a comment on JENKINS-42959
Re: Failed known_hosts verification for SSH agent
It seems like there's a legitimate bug here, where the SSH Slave Plugin SSH client doesn't report which host key types it supports. My hosts all have {{ssh-rsa}} and {{ecdsa-sha2-nistp256}} host keys, but because the client doesn't tell the host which one it wants, the host responds only with the {{ecdsa-sha2- nistp266 nistp256 }} key. This causes the plugin to fail to connect.
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-39832) org.eclipse.jgit.errors.MissingObjectException: Missing commi
Title: Message Title John Zila commented on JENKINS-39832 Re: org.eclipse.jgit.errors.MissingObjectException: Missing commi I restarted. 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-39832) org.eclipse.jgit.errors.MissingObjectException: Missing commi
Title: Message Title John Zila commented on JENKINS-39832 Re: org.eclipse.jgit.errors.MissingObjectException: Missing commi I had the errors in the log and new branches weren't getting builds. I've restarted Jenkins and now it's working: no errors in logs and new branches are getting picked up. 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-39832) org.eclipse.jgit.errors.MissingObjectException: Missing commi
Title: Message Title John Zila commented on JENKINS-39832 Re: org.eclipse.jgit.errors.MissingObjectException: Missing commi This is happening to me with autofavorite plugin v0.5 and git plugin v3.0.3 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-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title John Zila commented on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds Patrick Thiel: https://issues.jenkins-ci.org/browse/JENKINS-40652 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-40652) origin pr builds not treated as trusted
Title: Message Title John Zila commented on JENKINS-40652 Re: origin pr builds not treated as trusted +1. In my config this makes PR builds useless, because they're always building master. 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-41207) NullPointerException in Github branch source plugin after upgrading
Title: Message Title John Zila resolved as Fixed Thanks for all your help Stephen. My issue was partially because I was running beta versions of the plugins before so the upgrade path wasn't anticipated. I recovered my jobs from backup. After running the recommended master SNAPSHOT from the JENKINS-41209 fix, the jobs loaded correctly. Jenkins / JENKINS-41207 NullPointerException in Github branch source plugin after upgrading Change By: John Zila Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you
[JIRA] (JENKINS-41207) NullPointerException in Github branch source plugin after upgrading
Title: Message Title John Zila commented on JENKINS-41207 Re: NullPointerException in Github branch source plugin after upgrading If you mean the "Manage Old Data" admin screen, then that one is empty. 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-41207) NullPointerException in Github branch source plugin after upgrading
Title: Message Title John Zila commented on JENKINS-41207 Re: NullPointerException in Github branch source plugin after upgrading I don't see a data migration admin screen. Where would that be? 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-41207) NullPointerException in Github branch source plugin after upgrading
Title: Message Title John Zila commented on JENKINS-41207 Re: NullPointerException in Github branch source plugin after upgrading Emailed 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.
