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

Can't use environment variables in jenkinsfile script path for pipelines from SCM

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • pipeline
    • Latest Windows Server 2016 Standard
      Latest Jenkins + all plugins up to date
      SCM plugin: PlasticSCM Plugin

    Description

      PlasticSCM requires a system-wide unique workspace name. Therefore we use workspaces like "Pipelines_${NODE_NAME}" for check-out.

      When specifying the jenkinsfile (Script Path) for a pipeline job configuration the ${NODE_NAME} placeholder is not evaluated correctly. 

      Please see the attached inital_config.png for a pipeline configuration using PlasticSCM.

      When the job is run, there will be an ERROR: Jenkinsfile not found. As seen in attached error.png. 

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              swsbb Benjamin Buchfink
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: