• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: p4-plugin
• Labels:

  None
• Environment:

  p4-plugin 1.8.8
  jenkins 2.98

[JENKINS-50684] declarative pipeline P4_CHANGELIST + P4_CLIENT uses Jenkinsfile value, not workspace mapping in the Jenkinsfile script

Daniel Hsueh created issue - 2018-04-09 17:26

Daniel Hsueh made changes - 2018-04-09 17:28

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against JENKINS-42411 and JENKINS-38401 and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a "-jenkinsfile" suffix, and it automagically changes to "jenkinsTemp-(uuid)" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script 'jenkins-$\{NODE_NAME}-$\{JOB_NAME}' or 'jenkins-$\{JOB_NAME}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against -JENKINS-42411- and -JENKINS-38401- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '-jenkinsfile' suffix, and it automagically changes to "jenkinsTemp-(uuid)" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script 'jenkins-$\{NODE_NAME}-$\{JOB_NAME}' or 'jenkins-$\{JOB_NAME}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

Daniel Hsueh made changes - 2018-04-09 17:28

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against -JENKINS-42411- and -JENKINS-38401- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '-jenkinsfile' suffix, and it automagically changes to "jenkinsTemp-(uuid)" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script 'jenkins-$\{NODE_NAME}-$\{JOB_NAME}' or 'jenkins-$\{JOB_NAME}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against -JENKINS-42411- and -JENKINS-38401- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '\\-jenkinsfile' suffix, and it automagically changes to "jenkinsTemp\\-(uuid)" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script 'jenkins-$\{NODE_NAME}-$\{JOB_NAME}' or 'jenkins-$\{JOB_NAME}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

Daniel Hsueh made changes - 2018-04-09 17:30

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against -JENKINS-42411- and -JENKINS-38401- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '\\-jenkinsfile' suffix, and it automagically changes to "jenkinsTemp\\-(uuid)" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script 'jenkins-$\{NODE_NAME}-$\{JOB_NAME}' or 'jenkins-$\{JOB_NAME}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against -JENKINS-42411- and -JENKINS-38401- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp\-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME}\-$\{JOB_NAME}}}' or '{{jenkins\-$\{JOB_NAME}}}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

Daniel Hsueh made changes - 2018-04-09 17:32

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against -JENKINS-42411- and -JENKINS-38401- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp\-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME}\-$\{JOB_NAME}}}' or '{{jenkins\-$\{JOB_NAME}}}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against --JENKINS-42411-- and --JENKINS-38401-- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\}}}' or '{{jenkins\-$\{JOB_NAME\}}}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

Daniel Hsueh made changes - 2018-04-09 17:33

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against --JENKINS-42411-- and --JENKINS-38401-- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\}}}' or '{{jenkins\-$\{JOB_NAME\}}}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against --JENKINS-42411-- and --JENKINS-38401-- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp\-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\} }}' or '{{jenkins\-$\{JOB_NAME\} }}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

Daniel Hsueh made changes - 2018-04-09 17:34

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against --JENKINS-42411-- and --JENKINS-38401-- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp\-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\} }}' or '{{jenkins\-$\{JOB_NAME\} }}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against ---JENKINS-42411--- and ---JENKINS-38401--- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\}}}' or '{{jenkins\-$\{JOB_NAME\}}}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

Collapse comment: Daniel Hsueh added a comment - 2018-05-17 15:01

Daniel Hsueh added a comment - 2018-05-17 15:01

to clarify my submission description, I attempted the workarounds to no remedial effect

Expand comment: Daniel Hsueh added a comment - 2018-05-17 15:01

Daniel Hsueh added a comment - 2018-05-17 15:01 to clarify my submission description, I attempted the workarounds to no remedial effect

Daniel Hsueh made changes - 2018-09-14 18:58

Description

Original: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against ---JENKINS-42411--- and ---JENKINS-38401--- and attempted the workarounds. I usually name the workspace for Jenkinsfile checkout from SCM with a '{{\-jenkinsfile}}' suffix, and it automagically changes to "{{jenkinsTemp-(uuid)}}" at some point in time without my intervention, but in all cases the console output shows a uuid workspace or a workspace name different from my in-script '{{jenkins\-$\{NODE_NAME\}\-$\{JOB_NAME\}}}' or '{{jenkins\-$\{JOB_NAME\}}}' value.  The environment P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)

New: The P4_CHANGELIST and P4_CLIENT values seen in the environment end up with values from the Jenkinsfile checkout, and not from the workspace mapping in the script. I have checked against ---JENKINS-42411--- and ---JENKINS-38401--- and attempted the workarounds. For both lightweight and regular Jenkinsfile checkout cases the resulting P4_CHANGELIST and P4_CLIENT values reflect the script checkout, not the checkout invoked in the script. (The results of the checkout invoked in the script seem to have the correct perforce retrieval though.  The console output show the correct in-script workspace name used in p4 client/changes/reconcile/sync commands.)