Jenkinsfile per branch - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Jenkinsfile?

A Jenkinsfile is a text file that contains the pipeline code for Jenkins to automate tasks like building, testing, and deploying software.

beginner

Why use a Jenkinsfile per branch?

Using a Jenkinsfile per branch lets each branch have its own pipeline steps, so you can test or deploy differently depending on the branch.

intermediate

How does Jenkins decide which Jenkinsfile to use when building a branch?

Jenkins checks out the branch code and uses the Jenkinsfile found in that branch's root directory to run the pipeline.

intermediate

What is a simple way to test different Jenkinsfiles for different branches?

Create a Jenkinsfile in each branch with the specific pipeline steps you want, then Jenkins will run the pipeline from that file when building that branch.

beginner

Can you use a shared Jenkinsfile for all branches instead of one per branch?

Yes, you can use one Jenkinsfile for all branches, but using one per branch gives more flexibility to customize pipelines per branch.

What does Jenkins use to run a pipeline for a specific branch?

A A Jenkinsfile from a random branch

B A global Jenkinsfile from the master branch

C A Jenkinsfile stored on the Jenkins server only

D The Jenkinsfile in that branch's code

Jenkins uses the Jenkinsfile found in the checked-out branch to run the pipeline.

Why might you want a different Jenkinsfile per branch?

A To customize build and deploy steps per branch

B To confuse the Jenkins server

C Because Jenkins requires it

D To avoid using pipelines

Different branches can have different pipeline needs, so separate Jenkinsfiles allow customization.

If you add a Jenkinsfile only to the main branch, what happens when Jenkins builds a feature branch without a Jenkinsfile?

A Jenkins will use the main branch Jenkinsfile automatically

B Jenkins will create a Jenkinsfile for the branch

C Jenkins will fail or not run the pipeline

D Jenkins will skip the build

Jenkins looks for a Jenkinsfile in the branch; if missing, the pipeline cannot run.

How can you manage common pipeline steps across branches while using Jenkinsfile per branch?

A Use shared libraries or include common scripts

B Copy the entire Jenkinsfile manually to each branch

C Use no Jenkinsfile at all

D Run pipelines only on the master branch

Shared libraries let you reuse code while keeping branch-specific Jenkinsfiles.

What is the best practice for storing Jenkinsfiles in a Git repository?

A Store Jenkinsfile in a separate repository

B Store Jenkinsfile in the root directory of each branch

C Store Jenkinsfile only on the Jenkins server

D Store Jenkinsfile in a hidden folder outside the repo

Jenkins expects the Jenkinsfile in the root of the branch's code to run pipelines.

Explain how Jenkins uses Jenkinsfiles when building different branches in a Git repository.

Think about how Jenkins finds and runs pipeline code per branch.

Describe the advantages of having a Jenkinsfile per branch compared to a single Jenkinsfile for all branches.

Consider why branches might need different automation steps.