[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi edited a comment on JENKINS-43210 Re: Windows Agent can't connect to Master through JNLP [~gnuheidix] thank you for the information.We checked our Apache config too, but it seems, that our proxy do not reject this headers, so it have to be an other problem.But a workaround is for us currently to deploy first an old Jenkins version and then we can update it without any problems to the newest one.I tried it shortly again with the newest version of Jenkins (2.150.1) and one Slave on the same maschine. Both tests with Docker containers were successful on Windows and on Linux.As soon I can test it, I will try something with a proxy and over multiple servers, maybe it will work now. And I will update the plugins, maybe it is not an issue of Jenkins itself, it could be, that we hit it because of a plugin update. 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-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi commented on JENKINS-43210 Re: Windows Agent can't connect to Master through JNLP Thomas Heidrich thank you for the information. We checked our Apache config too, but it seems, that our proxy do not reject this headers, so it have to be an other problem. But a workaround is for us currently to deploy first an old Jenkins version and then we can update it without any problems to the newest one. I tried it shortly again with the newest version of Jenkins (2.150.1) and one Slave on the same maschine. Both tests with Docker containers were successful on Windows and on Linux. As soon I can test it, I will try something with a proxy and over multiple servers, maybe it will work now. 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-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi reopened an issue Jenkins / JENKINS-43210 Windows Agent can't connect to Master through JNLP Change By: Matthias Baldi Resolution: Won't Fix Status: Resolved Reopened 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-44772) User Scoped credentials are not used by the "withCredentials" pipeline step
Title: Message Title Matthias Baldi commented on JENKINS-44772 Re: User Scoped credentials are not used by the "withCredentials" pipeline step Thanks Peter Skopek for this PR, what is the actual state of this issue/PR? We have a similar problem, because we run deployments based to the user scoped credentials and this don't work since a while. So we would like to see this PR merged. 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-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi commented on JENKINS-43210 Re: Windows Agent can't connect to Master through JNLP We have currently also this issue with different versions of Jenkins 107.x, 121.x, 138.x with the JNLP v4 - all other protocols are disabled. As soon this problem occurs it does not matter if down- or upgrade the Jenkins instance, however it will occur every time. When we just enabled the JNLP v3 the Slave did not connect to the master and the container died after some seconds because of `no supported JNLP protocol`. We also tried your property Allan BURDAJEWICZ, but this does not changed the behavior. This issue does just occur with Jenkins instances we create since this summer, so there must be a change between May and July - maybe in the 107er versions. We know, when we deploy an older Jenkins version (like <=89x) it will work, but we do not know from where we get this Jenkins.io cert. Because the CN is not correct and we already set the Jenkins.io cert in the truststore, so it should be allowed and trusted. I think Jenkins generates this cert itself -> Can you Oleg Nenashev answer the question where this cert is generated and why? Is this a problem by updateing on a specific version of a plugin? Or is it a "problem" of Jenkins itself? For me, this issue is not solved. Following we add our configuration/logs: INFO: Trying protocol: JNLP4-connect Sep 19, 2018 11:25:02 AM org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer onRecv SEVERE: [JNLP4-connect connection to vjkm01.pnet.ch/172.18.15.26:33529] javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1529) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535) at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1214) at sun.security.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1186) at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:469) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processRead(SSLEngineFilterLayer.java:392) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecv(SSLEngineFilterLayer.java:117) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecv(ProtocolStack.java:669) at org.jenkinsci.remoting.protocol.impl.AckFilterLayer.onRecv(AckFilterLayer.java:255) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecv(ProtocolStack.java:669) at org.jenkinsci.remoting.protocol.NetworkLayer.onRead(NetworkLayer.java:136) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$2200(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:283) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1728) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:330) at
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi updated an issue Jenkins / JENKINS-43210 Windows Agent can't connect to Master through JNLP Change By: Matthias Baldi Attachment: image-2018-09-19-12-09-33-563.png 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-39110) The Pipeline load statement returns Null
Title: Message Title
Matthias Baldi commented on JENKINS-39110
Re: The Pipeline load statement returns Null
thx to Mike Kingsbury the following code worked for me groovy file:
public groovyFileMethod() {
stage('build') {
// do something
}
}
return this;
jenkins file:
sh 'wget to git url'
def grovvyLib = load 'groovyFile.groovy'
groovyLib.groovyFileMethod()
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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Matthias Baldi commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json The Problems are still existent in the Jenkins version 2.32.1 and the Bitbucket Plugin version 1.1.5. But sometimes the webhook works... Bitbucket gets every time a HTTP 200 response, but I think this is because of the ngnix reverse proxy. When I send the same request manually (with the same HTTP headers and the same body) I get an 500 error from Jenkins with the same output - described in this issue. javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["user"] not found. 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.
