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

Pipeline script from SCM does not resolve project parameter used in branch specifier

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • workflow-cps-plugin
    • None
    • Jenkins 2.32.3. All plugins up to date.

      This issue was marked as fixed in --JENKINS-28447--, however, I am still seeing this issue in 2.32.3 LTS (all plugins updated). The attached screenshots show the issue and the relevant project configuration.

       

       

          [JENKINS-43040] Pipeline script from SCM does not resolve project parameter used in branch specifier

          Alan Rickman added a comment -

          I see the same issue on Jenkins v2.19.4 with latest plugins.

          Downgrading Pipeline: Groovy (workflow-cps) to v2.28 fixes the issue.

          Alan Rickman added a comment - I see the same issue on Jenkins v2.19.4 with latest plugins. Downgrading Pipeline: Groovy (workflow-cps) to v2.28 fixes the issue.

          Shannon Kerr added a comment -

          This bug is a killer.  Is there any way to work around it?

          Shannon Kerr added a comment - This bug is a killer.  Is there any way to work around it?

          Jesse Glick added a comment -

          Parameter expansion is not supported for lightweight checkouts. Switch to heavyweight checkouts if you need this feature.

          Jesse Glick added a comment - Parameter expansion is not supported for lightweight checkouts. Switch to heavyweight checkouts if you need this feature.

          Brian Keyser added a comment - - edited

          If I understand your suggestion, Jesse, then build parameter substitution should work if "Lightweight checkout" is disabled (not checked).  Unfortunately, disabling lightweight checkout and specifying a parameter for the script path does not work.  More specifically, issue JENKINS-42836, details a situation whether the script path cannot be set using a parameter.

          Brian Keyser added a comment - - edited If I understand your suggestion, Jesse, then build parameter substitution should work if "Lightweight checkout" is disabled (not checked).  Unfortunately, disabling lightweight checkout and specifying a parameter for the script path does not work.  More specifically, issue  JENKINS-42836 , details a situation whether the script path cannot be set using a parameter.

          Jesse Glick added a comment -

          That is a separate issue.

          Jesse Glick added a comment - That is a separate issue.

            Unassigned Unassigned
            tman1978 Thomas Mann
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: