You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jenkins: 2.411
OS: Linux - 5.15.0-1039-azure
Java: 11.0.19 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
---
kubernetes:3950.v581298fa_e4e7
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller is the official container image running in kubernetes
The agent is the inbound-agent container image from the most recent jdk11-nanoserver-1809 (3131.vf2b_b_798b_ce99-1-jdk11-nanoserver-1809)
Reproduction steps
Install the kubernetes plugin and configure it to a cluster with "Direct Connection" enabled.
Try to create a windows inbound agent.
It will fail to startup because it throws an error that JENKINS_URL is not defined.
If you manually define this in your pod template, then it will fail because JENKINS_URL and JENKINS_DIRECT_CONNECTION cannot both be set.
Expected Results
I should be able to connect with "Direct Connection" using the Windows inbound-agent like I can the linux ones.
Actual Results
It will fail to startup because it throws an error that JENKINS_URL is not defined.
If you manually define JENKINS_URL in your pod template, then it will fail because JENKINS_URL and JENKINS_DIRECT_CONNECTION cannot both be set.
Anything else?
The root of the issue appears to be on line 26 on jenkins-agent.ps1 in that it requires JENKINS_URL environment variable to always be set.
This is different to the behavior of the bash script and it also means that it is not possible to use "Direct Connection" (JNLP) with the windows inbound agent image.
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
inbound-agent
container image from the most recent jdk11-nanoserver-1809 (3131.vf2b_b_798b_ce99-1-jdk11-nanoserver-1809
)Reproduction steps
JENKINS_URL
is not defined.JENKINS_URL
andJENKINS_DIRECT_CONNECTION
cannot both be set.Expected Results
I should be able to connect with "Direct Connection" using the Windows inbound-agent like I can the linux ones.
Actual Results
JENKINS_URL
is not defined.JENKINS_URL
in your pod template, then it will fail becauseJENKINS_URL
andJENKINS_DIRECT_CONNECTION
cannot both be set.Anything else?
The root of the issue appears to be on line 26 on jenkins-agent.ps1 in that it requires
JENKINS_URL
environment variable to always be set.This is different to the behavior of the bash script and it also means that it is not possible to use "Direct Connection" (JNLP) with the windows inbound agent image.
The text was updated successfully, but these errors were encountered: