-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
Jenkins ver. 2.62
P4Plugin 1.7.0
Windows 7
We are building different streams using Multibranch Pipeline.
We set the Workspace Name Format to "jenkins-${NODE_NAME}-${JOB_NAME}".
For each stream, we build for different platforms, and the builds take place on different machines using nodes in parallel builds.
When we do a checkout scm on the distant node, the $NODE_NAME variable is resolved to an mangled string containing the hostname, ip address and port of the incoming connection from the master instead of just the node name:
[Pipeline] [Windows-x86-Debug] checkout [Windows-x86-Debug] (p4):cmd:... p4 client -o jenkins-JNLP4-connect_connection_from_mycomputer.mydomain.com-10.127.20.3___ [Windows-x86-Debug] p4 client -o jenkins-JNLP4-connect_connection_from_mycomputer.mydomain.com-10.127.20.38:60359-main [Windows-x86-Debug] [Windows-x86-Debug] (p4):stop:4 [Windows-x86-Debug] (p4):cmd:... p4 info [Windows-x86-Debug] p4 info [Windows-x86-Debug] [Windows-x86-Debug] (p4):stop:5 [Windows-x86-Debug] (p4):cmd:... p4 client -o jenkins-JNLP4-connect_connection_from_mycomputer.mydomain.com-10.127.20.3___ [Windows-x86-Debug] p4 client -o jenkins-JNLP4-connect_connection_from_mycomputer.mydomain-10.127.20.38:60359-main [Windows-x86-Debug] [Windows-x86-Debug] (p4):stop:6 [Windows-x86-Debug] (p4):cmd:... p4 client -i [Windows-x86-Debug] p4 client -i
The build itself is not affected, but this creates a huge amount of clients in P4 because the port number changes every new build.
[JENKINS-44546] NODE_NAME variable resolved to hostname+ip+port of connection when running parallel on distant node
antoine terrienne
created issue -
Karl Wirth
made changes -
| Labels | New: P4_SUPPORT |
Karl Wirth
made changes -
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |