I use the docker plugin to execute jobs remote in another docker-container. I configured the cloud with default parameters and the "connect method": "Attach Docker container". When i execute a job, i get the message, that the used parameter "-slaveLog" is invalid.
The reason for that is, that Jeff removed the parameter alias in version 4.6 of remoting.jar so just "-agentLog" is valid now (pull request here). With jenkins 2.266 the remote-4.6.jar is the new default, so the docker-plugin's default settings (for the "Attach" method) are no longer viable - it's now necessary to override the defaults to make it work.
[JENKINS-64251] Remote.jar is not working anymore because of changed parameter slave.jar->agent.jar
Link | New: This issue duplicates INFRA-2817 [ INFRA-2817 ] |
Summary | Original: Remote.jar is not working anymore becuase of changed parameter slave.jar->agent.jar | New: Remote.jar is not working anymore because of changed parameter slave.jar->agent.jar |
Environment |
Original:
Jenkins 266 (not solved 267)
Docker plugin 1.2.1 OS Debian 9 Jenkins in Docker container (Based on Debian) Jenkins-Slave Docker Image (Based on Debian) Java 11 is used in master and slave container |
New:
Jenkins 266 (not solved in 267)
Docker plugin 1.2.1 OS Debian 9 Jenkins in Docker container (Based on Debian) Jenkins-Slave Docker Image (Based on Debian) Java 11 is used in master and slave container |
Environment |
Original:
Jenkins 266 (not solved in 267)
Docker plugin 1.2.1 OS Debian 9 Jenkins in Docker container (Based on Debian) Jenkins-Slave Docker Image (Based on Debian) Java 11 is used in master and slave container |
New:
Jenkins 266 (not solved in 267)
Docker plugin 1.2.1 OS Debian 9 Docker version 19.03.13 Jenkins in Docker container (Based on Debian) Jenkins-Slave Docker Image (Based on Debian) Java 11 is used in master and slave container |
Comment | [ I accidentaly created the issue INFRA-2817 before, but i am not able to delete that. ] |
Environment |
Original:
Jenkins 266 (not solved in 267)
Docker plugin 1.2.1 OS Debian 9 Docker version 19.03.13 Jenkins in Docker container (Based on Debian) Jenkins-Slave Docker Image (Based on Debian) Java 11 is used in master and slave container |
New:
Jenkins 2.266 (not solved in 267)
Docker plugin 1.2.1 OS Debian 9 Docker version 19.03.13 Jenkins in Docker container (Based on Debian) Jenkins-Slave Docker Image (Based on Debian) Java 11 is used in master and slave container |
Description |
Original:
I use the docker plugin to execute jobs remote in another docker-container. I configured the cloud with default parameters and the "connect method": "Attach Docker container". When i execute a job, i get the message, that the used parameter "-slaveLog" is invalid.
The reason for that is, that Jeff removed t[he parameter alias|https://groups.google.com/g/jenkinsci-users/c/ZWdWjYbfmPI] in version 4.6 of remoting.jar so just "-agentLog" is valid now (pull request [here|https://github.com/jenkinsci/remoting/pull/416]). With jenkins 2.266 the remote-4.6.jar is the new default, so no builds are possible now with docker plugin. |
New:
I use the docker plugin to execute jobs remote in another docker-container. I configured the cloud with default parameters and the "connect method": "Attach Docker container". When i execute a job, i get the message, that the used parameter "-slaveLog" is invalid.
The reason for that is, that Jeff removed t[he parameter alias|https://groups.google.com/g/jenkinsci-users/c/ZWdWjYbfmPI] in version 4.6 of remoting.jar so just "-agentLog" is valid now (pull request [here|https://github.com/jenkinsci/remoting/pull/416]). With jenkins 2.266 the remote-4.6.jar is the new default, so the docker-plugin's default settings (for the "Attach" method) are no longer viable - it's now necessary to override the defaults to make it work. |
Assignee | Original: Nicolas De Loof [ ndeloof ] | New: pjdarton [ pjdarton ] |
The original descripiton said "no builds are possible now" - that was incorrect ... builds are still possible; the problem is that the default settings are no longer viable (if you override them, it can still work).
See this comment in docker-plugin issue 818 for details of the workaround.