[JIRA] (JENKINS-60213) P4CLIENT environment variable non-reentrant
Title: Message Title
Tom Reed edited a comment on JENKINS-60213
Re: P4CLIENT environment variable non-reentrant
I have been battling a similar issue.My situation is that the P4_CLIENT I build uses the variables "jenkins-${JOB_NAME}-\{NODE_NAME}"The NODE_NAME is wrong a few times a night with 6 parallel builds on 6 different nodes. About 40-050 builds are queued a night, and the wrong P4_CLIENT is causing the wrong P$_CHANGELIST P4_CHANGELIST to be reported.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.6941.1584123120180%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4CLIENT environment variable non-reentrant
Title: Message Title
Tom Reed commented on JENKINS-60213
Re: P4CLIENT environment variable non-reentrant
I have been battling a similar issue. My situation is that the P4_CLIENT I build uses the variables "jenkins-${JOB_NAME}-{NODE_NAME}" The NODE_NAME is wrong a few times a night with 6 parallel builds on 6 different nodes. About 40-050 builds are queued a night, and the wrong P4_CLIENT is causing the wrong P$_CHANGELIST to be reported.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.6938.1584123060290%40Atlassian.JIRA.
