PR https://github.com/jenkinsci/remoting/pull/202

Code changed in jenkins
User: Carlos Sanchez
Path:
src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java
http://jenkins-ci.org/commit/remoting/a450c9e4d9dbd235cdd91af04f53a500a3a55788
Log:
JENKINS-47425 Do not print a stack trace on connection error (#202)

• Do not print a stack trace on connection error

It is a possible condition and just pollutes the logs

• JENKINS-47425 Do not print a stack trace on remoting connection error

It is a possible condition and just pollutes the logs

• retry again -> try again

Code changed in jenkins
User: Oleg Nenashev
Path:
pom.xml
http://jenkins-ci.org/commit/jenkins/bcd0b2c72bf8c55b7d4997e142954c149b7d4faa
Log:
Update Remoting from 3.13. to 3.14

Fixes JENKINS-45294, JENKINS-47425, JENKINS-47901, JENKINS-47942 + about 50 reported FindBugs issues (JENKINS-37566). There are 13 FindBugs issues left, work in progress.

The patch has been released in Remoting 3.14 and integrated towards Jenkins 2.90

Code changed in jenkins
User: Oleg Nenashev
Path:
pom.xml
http://jenkins-ci.org/commit/jenkins/94250ec1caae0ed6d3096e7002e0c2fd42c557e1
Log:
Update Remoting from 3.13. to 3.14

Fixes JENKINS-45294, JENKINS-47425, JENKINS-47901, JENKINS-47942 + about 50 reported FindBugs issues (JENKINS-37566). There are 13 FindBugs issues left, work in progress.

(cherry picked from commit bcd0b2c72bf8c55b7d4997e142954c149b7d4faa)

Compare: https://github.com/jenkinsci/jenkins/compare/c624f66dc408...94250ec1caae