[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191

jthompson@cloudbees.com (JIRA)

unread,

Aug 28, 2019, 6:27:02 PM8/28/19

to jenkinsc...@googlegroups.com

Jeff Thompson commented on

JENKINS-59094

Re: Agent tunnel connection issues after ugrading Jenkins to 2.191

I updated the title to something that I think is a little clearer and more accurate.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jthompson@cloudbees.com (JIRA)

unread,

Aug 28, 2019, 6:27:02 PM8/28/19

to jenkinsc...@googlegroups.com

Jeff Thompson updated an issue

Jenkins /

JENKINS-59094

Agent tunnel connection issues after ugrading Jenkins to 2.191

Change By:	Jeff Thompson
Summary:	Windows Agent tunnel connection issues after ugrading Jenkins to 2.191

Add Comment

dzianis.mazuronak@swisspost.com (JIRA)

unread,

Aug 30, 2019, 3:25:02 PM8/30/19

to jenkinsc...@googlegroups.com

Dzianis Mazuronak edited a comment on

JENKINS-59094

Re: Agent tunnel connection issues after ugrading Jenkins to 2.191

Here is the jenkins-slave.xml file from my windows slave xxxxxx05ws016:

{code:xml}
<service>
  <id>jenkinsslave-C__projects_jenkins</id>
  <name>Jenkins agent (jenkinsslave-C__projects_jenkins)</name>
  <description>This service runs an agent for Jenkins automation server.</description>
  <executable>C:\Program Files (x86)\AdoptOpenJDK\jre-8.0.222.10-hotspot\bin\java.exe</executable>
  <arguments>-Xrs  -jar "%BASE%\slave.jar" -jnlpUrl https://tools.xxxxx.local/devjenkins/computer/xxxxx05ws016/slave-agent.jnlp -secret XXXXXXXXXXX -noCertificateCheck</arguments>
  <logmode>rotate</logmode>
  <onfailure action="restart" />
  <download from="https://tools.xxxxx.local/devjenkins/jnlpJars/slave.jar" to="%BASE%\slave.jar"/>
  <extensions>
    
    <extension enabled="true"
               className="winsw.Plugins.RunawayProcessKiller.RunawayProcessKillerExtension"
               id="killOnStartup">
      <pidfile>%BASE%\jenkins_agent.pid</pidfile>
      <stopTimeout>5000</stopTimeout>
      <stopParentFirst>false</stopParentFirst>
    </extension>
  </extensions>
</service>
{code}

Unfortunately, I'll *not* be able to test your PR. Compiling Jenkins from the source code is not a easy task.

Add Comment

jthompson@cloudbees.com (JIRA)

unread,

Aug 30, 2019, 3:31:02 PM8/30/19

to jenkinsc...@googlegroups.com

Jeff Thompson commented on

JENKINS-59094

Re: Agent tunnel connection issues after ugrading Jenkins to 2.191

Dzianis Mazuronak, I had planned to have an incrementals version published to the Jenkins Artifactory repository that you could consider testing. Unfortunately, it's not fully set up for that yet, but there are changes in the works to enable it. Without that, it is definitely harder to test.

I'll see if anyone else is able to perform any reviews or tests. I hope to get Remoting released early next and included in the following Jenkins weekly.

Add Comment

o.v.nenashev@gmail.com (JIRA)

unread,

Aug 30, 2019, 5:00:02 PM8/30/19

to jenkinsc...@googlegroups.com

Oleg Nenashev commented on

JENKINS-59094

Re: Agent tunnel connection issues after ugrading Jenkins to 2.191

https://github.com/jenkinsci/jenkins/pull/4186 for a temporary regression fix until the new version of Remoting is ready

Add Comment

o.v.nenashev@gmail.com (JIRA)

unread,

Sep 2, 2019, 3:18:01 AM9/2/19

to jenkinsc...@googlegroups.com

Oleg Nenashev commented on

JENKINS-59094

Re: Agent tunnel connection issues after ugrading Jenkins to 2.191

A workaround has been released in 2.193. We hope to have a Remoting fix in the next releases

Add Comment

o.v.nenashev@gmail.com (JIRA)

unread,

Sep 5, 2019, 6:38:06 AM9/5/19

to jenkinsc...@googlegroups.com

Oleg Nenashev started work on

JENKINS-59094

Change By:	Oleg Nenashev
Status:	Open In Progress

Add Comment

jthompson@cloudbees.com (JIRA)

unread,

Sep 6, 2019, 2:00:02 PM9/6/19

to jenkinsc...@googlegroups.com

Jeff Thompson commented on

JENKINS-59094

Re: Agent tunnel connection issues after ugrading Jenkins to 2.191

The problem turned out to be related to tunneling configurations, when the tunnel HOST:PORT is missing the HOST and / or PORT specification. In my change for Remoting 3.34, I had missed some magic whereby the values are filled in from prior sources. Remoting 3.3.5 restores these configuration paths / options and retains the new capabilities introduced in 3.34. I couldn't find any connection between this issue and the Windows platform, as the original title stated, so I've changed the title to better reflect the actual issue.