-
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
Dalen Kruse
added a comment - This issue might be fixed with P4Plugin v1.8.1 (Refer to change 23190 in the release notes). Are you still seeing this issue?
Dalen Kruse
added a comment - This issue might be fixed with P4Plugin v1.8.1 (Refer to change 23190 in the release notes ). Are you still seeing this issue? 
Karl Wirth
added a comment - Unable to reproduce this when using a Windows build slave. If this is still a problem please let me know:
- slave OS version
- master OS version
- how the build slave is started
- Is the a permanent build slave predefined in Jenkins or is it a pop up slave that is created by something such as Docker.
- Current Jenkins version
- Current P4Jenkins version.
Thanks in advance.
Note: I'm going to close this now but if it is still a problem please reopen and I'll also work with you directly through our support channel.
Karl Wirth
added a comment - Unable to reproduce this when using a Windows build slave. If this is still a problem please let me know:
slave OS version
master OS version
how the build slave is started
Is the a permanent build slave predefined in Jenkins or is it a pop up slave that is created by something such as Docker.
Current Jenkins version
Current P4Jenkins version.
Thanks in advance.
Note: I'm going to close this now but if it is still a problem please reopen and I'll also work with you directly through our support channel. Karl Wirth
added a comment - Will work directly with Antoine if this is still a problem. 
Also seeing this. NODE_NAME seems to contain the JNLP connect string.