Jenkins multibranch "Jenkinsfile not found" / no Jenkinsfile in CI

A multibranch or "Pipeline script from SCM" job reads the pipeline from a file in the repository. If that file is missing at the configured Script Path on a branch, Jenkins reports the Jenkinsfile as not found and does not build the branch.

What this error means

A branch is skipped in a multibranch scan with Jenkinsfile not found, or a Pipeline-from-SCM build fails because the script path does not resolve.

Checking out git repo ...
Obtained Jenkinsfile from <sha>
ERROR: /home/jenkins/workspace/app@script: Jenkinsfile not found
Finished: NOT_BUILT

Common causes

The Script Path is wrong or the file is absent

The job's Script Path (default Jenkinsfile) does not match where the file lives, or the branch genuinely has no Jenkinsfile.

The file exists only on some branches

In multibranch jobs, branches without a Jenkinsfile at the configured path are intentionally not built.

How to fix it

Align the Script Path with the repo

1. Confirm the file path in the repository for the affected branch.
2. Set the job's "Script Path" to that exact path (for example ci/Jenkinsfile).
3. Add the Jenkinsfile to branches that should build, or accept that branches without it are skipped.

# Job config -> Pipeline -> Script Path
ci/Jenkinsfile

How to prevent it

• Keep a consistent Script Path across branches.
• Add the Jenkinsfile to long-lived branches that must be built.
• Document that branches without the script are intentionally skipped.

Related guides