Thanks for having a look. I added the BuildWatcher and also changed the URL to "http://localhost"; but it doesn't change anything in the result. Comparing the stacktraces I can see that in my case the exception is already thrown in "org.codehaus.cargo.container. tomcat.internal.TomcatManager.invoke(TomcatManager.java:567)" calling "connection.connect();" while your linux build goes further and correctly throws the expected exception when reading the response calling "response = toString(connection.getInputStream(), MANAGER_CHARSET);".
So the question remains what could cause my system to throw a connection refused while others don't... On Tuesday, 23 July 2019 16:20:31 UTC+2, Jesse Glick wrote: > > I filed https://github.com/jenkinsci/deploy-plugin/pull/38 with some > hints. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8b3c5cbd-396b-4e7b-82ba-3971f0e7c27c%40googlegroups.com.
