Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50684

declarative pipeline P4_CHANGELIST + P4_CLIENT uses Jenkinsfile value, not workspace mapping in the Jenkinsfile script

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Labels:
      None
    • Environment:
      p4-plugin 1.8.8
      jenkins 2.98
    • Similar Issues:

      Description

      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.)

        Attachments

          Activity

          Hide
          dchsueh Daniel Hsueh added a comment -

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

          Show
          dchsueh Daniel Hsueh added a comment - to clarify my submission description, I attempted the workarounds to no remedial effect

            People

            • Assignee:
              Unassigned
              Reporter:
              dchsueh Daniel Hsueh
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: