如何解决从指定文件夹运行Jenkinsfile时文件未被检测到的问题

Let’s walk through the most common fixes for this issue— I’ve run into similar headaches plenty of times, so these steps should help you track down the root cause:

1. Verify Repository Structure & Case Sensitivity #

First, double-check your local repo to confirm:

• The pipelinescript folder lives directly in the repository root (not nested inside another directory).
• Folder and file names match exactly what you entered in Jenkins— Jenkins paths are case-sensitive! For example, PipelineScript/Jenkinsfile won’t match pipelinescript/Jenkinsfile.

2. Fix the Script Path Format #

When using "Pipeline script from SCM", Jenkins expects a relative path from the repo root— the leading slash (/) might be breaking path resolution. Try updating your script path to:

pipelinescript/Jenkinsfile

(Remove the leading /, save the job config, and re-run the build.)

3. Confirm SCM is Pulling the Correct Code #

If your job uses Git or another SCM, make sure:

• You’ve selected the right branch (the one that actually contains your pipelinescript/Jenkinsfile).
• Your SCM credentials have permission to pull the latest code— sometimes Jenkins gets stuck on an old commit that doesn’t include your new folder.
• Trigger a "Poll SCM" or re-run the job with "Build now" to ensure fresh code is pulled into the Jenkins workspace.

4. Debug by Inspecting the Jenkins Workspace #

Add a temporary build step to list workspace contents— this will confirm if the pipelinescript folder is even being pulled in:

• For Linux agents: Add an "Execute shell" step with:

  ls -la
  

• For Windows agents: Add an "Execute Windows batch command" step with:

  dir
  

Check the console output after running the job. If pipelinescript isn’t listed, the issue is with your SCM setup (not the Jenkinsfile path).

5. Check File/Folder Permissions (For Local Repos) #

If you’re using a local repository (not remote SCM), ensure the Jenkins service user has read access to the pipelinescript folder:

• On Linux, run these commands to set proper permissions:

  sudo chown -R jenkins:jenkins /path/to/your/repo
  sudo chmod -R 755 /path/to/your/repo/pipelinescript
  

This ensures Jenkins can read the files in that directory.

内容的提问来源于stack exchange，提问作者Parnash