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

CPPScmFlowDefinition with the ability to use the job name in the scm path

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Duplicate
    • Icon: Minor Minor
    • workflow-cps-plugin
    • None

      Would be useful when the scm path from which the groovy file is loaded could use variables like the job name so that we easily can copy jobs, just give them an unique name and the scm path doesn't need to manually maintained. Made an initial comment on this on JENKINS-28447

        1. config.xml
          2 kB

          [JENKINS-38439] CPPScmFlowDefinition with the ability to use the job name in the scm path

          Johnny Willemsen added a comment -

          So in the attached config.xml support for replacing

          <scriptPath>taox11/rhel65_taox11.groovy</scriptPath>

          with

          <scriptPath>taox11/${JOB_NAME}.groovy</scriptPath>

          Johnny Willemsen added a comment - So in the attached config.xml support for replacing <scriptPath>taox11/rhel65_taox11.groovy</scriptPath> with <scriptPath>taox11/${JOB_NAME}.groovy</scriptPath>

          Andrew Bayer added a comment -

          This is the same root issue as JENKINS-42836, so closing as a dupe.

          Andrew Bayer added a comment - This is the same root issue as JENKINS-42836 , so closing as a dupe.

            Unassigned Unassigned
            jwillemsen Johnny Willemsen
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: