When using "Pipeline script from SCM" has the download directory for the pipeline script changed?

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Not A Defect
    • Priority: Minor
    • Environment:

      We use the "Pipeline script from SCM" option to download our pipeline script from gitlab. The script (and the rest of the repository) used to be downloaded to the directory:

      ${JENKINS_HOME}/workspace/${JOB_NAME}@script/

      For example, for a job called jobX, this would be:

      /var/lib/jenkins/workspace/jobX@script/

      But now it is downloaded to a subdirectory:

      /var/lib/jenkins/workspace/jobX@script/76f4045e36944bf2082584f9eefeac03f558748a305ceb0127c76e11b366e363

      This is all happening on the master node.

      The problem is that the pipeline script refers to other files in the same directory and those references don't work because the directory name has changed.

      I think the change was masked because the @script directory is not cleaned out so the old contents remained. Old jobs seemed to carry on working but a new job did not.

            Assignee:
            Unassigned
            Reporter:
            Dave
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: