-
Bug
-
Resolution: Unresolved
-
Critical
-
None
In kubernetes plugin between 1.24.1 and 1.25.4 the working directory of the jnlp template seems to have changed to include the job name.
In "Configure Clouds": How do I define the matching working directory in a container template?
Do I now need to configure the jnlp template that was implicitly defined previously?
I tried to use ${WORKSPACE} in the template configuration, that did not work.
Working dir in implicit jnlp template (now):
/home/jenkins/agent/workspace/<Job-Name>
Default for other containers (and jnlp previously):
/home/jenkins/agent
[JENKINS-62252] Working directory of jnlp container has changed
Description |
Original:
In kubernetes plugin between 1.24.1 and 1.25.4 the working directory of the jnlp template seems to have changed to include the job name. In "Configure Clouds": How do I define the matching working directory in a container template? Do I now need to configure the jnlp template that was implicitly defined previously? I tried to use ${WORKSPACE} in the template configuration, that did not work. Working dir in implicit jnlp template (now): /home/jenkins/agent/workspace/<Job-Name> Default for container (and jnlp previously): /home/jenkins/agent |
New:
In kubernetes plugin between 1.24.1 and 1.25.4 the working directory of the jnlp template seems to have changed to include the job name. In "Configure Clouds": How do I define the matching working directory in a container template? Do I now need to configure the jnlp template that was implicitly defined previously? I tried to use ${WORKSPACE} in the template configuration, that did not work. Working dir in implicit jnlp template (now): /home/jenkins/agent/workspace/<Job-Name> Default for other containers (and jnlp previously): /home/jenkins/agent |
Attachment | New: working_dir.png [ 51193 ] |