Closed schroedt closed 1 year ago
This is still an issue. https://github.com/jenkinsci/docker-inbound-agent/releases shows that 4.13-2 is the most recent release, yet the output of the commands shows that jenkins/inbound-agent:latest
is reporting version 4.10 instead of 4.13.
$ docker run --rm -i -t jenkins/inbound-agent:latest -version
4.10
$ docker run --rm -i -t jenkins/inbound-agent:4.13-2 -version
4.13
Expected output from docker run --rm -i -t jenkins/inbound-agent:latest -version
is 4.13
, not 4.10
The problem also manifests itself when deploying to the cloud using Helm.
The agent version specified in the podTemplate is ignored. It was revealed that the removal and re-deployment of Jenkins leads to an update of the used version of the agent. Which is probably equivalent to re-installing on the local machine.
Currently, the "jenkins/inbound-agent" version is used:4.11-1-jdk11". Despite the fact that the command: docker ru --rmit jenkins/inbound-agent:latest -version outputs "4.10".
Where does "4.11-1-jdk11" come from???
CasS outputs the version of the agent for deployment specified in the podTemplate.
Source code, Helm output, Jenkins configs non't contain "4.11-1-jdk11" (((
is in not true that 'latest' does not refer to the latest version of an image?
Hi, this issue is not related to the official Docker controller image but to the Kubernetes Plugin: there are no change in this repository that could help in the described problem.
Also, since May 2022, the Kubernetes plugin did regularly update the default image using the following Dockerfile
: https://github.com/jenkinsci/kubernetes-plugin/blob/442524fea3d730812196f9fc5dd4d01109a255e9/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/Dockerfile#L1
As such, I'm gonna close this issue as completed.
It works. In my case, Jenkins rebooted and updated automatically. I've updated the Docker image 4.13. but, It still shows the log below. You saved my ass. Thanks.
java.io.IOException: Agent version 4.13 or newer is required. at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:229) at hudson.remoting.Engine.innerRun(Engine.java:724) at hudson.remoting.Engine.run(Engine.java:540)
Hi, this issue is not related to the official Docker controller image but to the Kubernetes Plugin: there are no change in this repository that could help in the described problem.
Also, since May 2022, the Kubernetes plugin did regularly update the default image using the following
Dockerfile
: https://github.com/jenkinsci/kubernetes-plugin/blob/442524fea3d730812196f9fc5dd4d01109a255e9/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/Dockerfile#L1As such, I'm gonna close this issue as completed.
Version report
Jenkins and plugins versions report:
Reproduction steps
Trigger a build of any project. Stated
jenkins/inbound-agent:latest
resolves tojenkins/inbound-agent:4.3.4-jdk11
(not correct) instead of4.10-3-jdk11
(correct).Following https://plugins.jenkins.io/kubernetes/, I can overwrite the default agent image at Jenkinsfile (which resolves the issue of running an outdated container):
Results
Expected result:
JNLP is using
latest
or4.10-3-jdk11
or newer (if available). Instead a tagged version is used, instead of configured one. I was able to update the container namejenkins-slave
»jnlp
. Tag is not updated.Actual result: