Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
CentOS root node and 2 macOS agents connecting to it through JNLP4.
Description
Seeing something that sounds similar to https://issues.jenkins-ci.org/browse/JENKINS-48754.
"After having installed Jenkins Version 2.99, none of my agents did connect to the server anymore. Even a restart of the java script on the slave did not help."
Workaround: Update Remoting on the agent side to 3.15
Agent is launched like so:
java -jar agent.jar -jnlpUrl https://<Jenkins URL>/computer/<AgentName>/<>.jnlp -secret <Agent Secret>
Attachments
Issue Links
- is duplicated by
-
JENKINS-48760 Jenkins Slaves do not connect after update from version 2.95 to version 2.99 and jobs fail
-
- Resolved
-
- is related to
-
JENKINS-48754 Jenkins Slaves do not connect after update from version 2.95 to version 2.99
-
- Resolved
-
-
JENKINS-48766 Jenkins Core should provide info about minimum supported Remoting version in API/REST API/logs
-
- Resolved
-
- links to
Code changed in jenkins
User: Oleg Nenashev
Path:
core/src/filter/resources/jenkins/slaves/remoting-info.properties
core/src/main/java/hudson/Launcher.java
core/src/main/java/hudson/TcpSlaveAgentListener.java
core/src/main/java/hudson/model/Computer.java
core/src/main/java/hudson/slaves/SlaveComputer.java
core/src/main/java/jenkins/security/MasterToSlaveCallable.java
core/src/main/java/jenkins/slaves/RemotingVersionInfo.java
core/src/test/java/jenkins/slaves/RemotingVersionInfoTest.java
pom.xml
test/pom.xml
test/src/test/java/jenkins/slaves/OldRemotingAgentTest.java
http://jenkins-ci.org/commit/jenkins/8eb4254b0f56086f6576c108913fc5d066f4be9b
Log:
Merge pull request #3212 from oleg-nenashev/bug/
JENKINS-48761-remoting-APIJENKINS-48761- Restore binary compatibility with agents running old Remoting versionsCompare: https://github.com/jenkinsci/jenkins/compare/99ca10114332...8eb4254b0f56