Multi-branch pipeline job creation in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary purpose of a Jenkins multi-branch pipeline?

Choose the best description of what a Jenkins multi-branch pipeline job does.

A It schedules pipeline jobs only for the main branch of a repository.

B It runs a single pipeline job that merges all branches before building.

C It automatically discovers branches in a source code repository and creates pipelines for each branch.

D It creates a pipeline that runs only when manually triggered.

💡 Hint

Think about how Jenkins handles multiple branches in one job.

A multi-branch pipeline automatically detects branches in your repository and creates separate pipeline jobs for each branch, enabling parallel and independent builds.

💻 Command Output

intermediate

What is the output of this Jenkinsfile snippet in a multi-branch pipeline?

Given the Jenkinsfile below, what will be printed when the pipeline runs on branch 'feature-xyz'?

Jenkins

pipeline {
  agent any
  stages {
    stage('Print Branch') {
      steps {
        echo "Building branch: ${env.BRANCH_NAME}"
      }
    }
  }
}

A Building branch: null

B Building branch: feature-xyz

C Building branch: main

D Syntax error in Jenkinsfile

💡 Hint

Check the environment variable that Jenkins sets for branch name in multi-branch pipelines.

The environment variable BRANCH_NAME contains the current branch name in a multi-branch pipeline, so it prints 'feature-xyz' when building that branch.

❓ Configuration

advanced

Which Jenkinsfile snippet correctly triggers builds only for branches with names starting with 'release/'?

Select the Jenkinsfile snippet that uses the correct syntax to include only branches starting with 'release/' in a multi-branch pipeline.

A options { skipDefaultCheckout() }

B triggers { pollSCM('H/5 * * * *') }

C properties([pipelineTriggers([branchFilter('release/*')])])

D when { branch pattern: 'release/.*', comparator: 'REGEXP' }

💡 Hint

Look for the correct way to filter branches in Jenkinsfile using 'when' and 'branch' conditions.

The when directive with branch pattern: 'release/.*', comparator: 'REGEXP' correctly filters builds to run only on branches matching the pattern.

🔀 Workflow

advanced

What is the correct sequence to create a Jenkins multi-branch pipeline job for a GitHub repository?

Order the steps to create a multi-branch pipeline job that builds branches from a GitHub repository.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about the logical order of creating a new job and configuring it.

You first create a new item, select multi-branch pipeline, configure the repository, then save to trigger branch scanning.

❓ Troubleshoot

expert

Why does a Jenkins multi-branch pipeline fail to detect new branches after adding them to the repository?

You added new branches to your GitHub repository, but Jenkins multi-branch pipeline job does not create jobs for them. What is the most likely cause?

A The Jenkins job's branch source scan interval is too long or manual scan was not triggered.

B The Jenkinsfile is missing from the new branches.

C The GitHub repository URL is incorrect in the job configuration.

D The Jenkins master node is offline.

💡 Hint

Consider how Jenkins discovers new branches in multi-branch pipelines.

Jenkins scans the repository periodically or when manually triggered. If the scan interval is long or no manual scan is done, new branches won't be detected immediately.

Practice

1. What is the main purpose of a multi-branch pipeline job in Jenkins?

easy

A. To automatically create and manage pipeline jobs for each branch in a repository

B. To run a single pipeline job for all branches combined

C. To manually configure pipelines for each branch separately

D. To deploy applications without building them

Solution

1. Step 1: Understand multi-branch pipeline concept

   A multi-branch pipeline job automatically detects branches in a source code repository and creates pipeline jobs for each branch.

2. Step 2: Compare options with concept

   To automatically create and manage pipeline jobs for each branch in a repository correctly describes this automation. Options B, C, and D do not match the automatic branch job creation feature.

3. Final Answer:

   To automatically create and manage pipeline jobs for each branch in a repository -> Option A

4. Quick Check:

   Multi-branch pipeline = automatic branch job creation [OK]

Hint: Multi-branch pipelines auto-create jobs per branch [OK]

Common Mistakes:

• Thinking it runs one job for all branches
• Assuming manual job creation is needed
• Confusing deployment with pipeline creation

2. Which Jenkinsfile location is automatically used by a multi-branch pipeline job for each branch?

easy

A. Only in the main branch

B. In a separate centralized folder outside branches

C. In the root directory of each branch

D. In the Jenkins server workspace

Solution

1. Step 1: Identify Jenkinsfile location for multi-branch pipelines

   Multi-branch pipelines look for a Jenkinsfile in the root directory of each branch to define that branch's pipeline.

2. Step 2: Evaluate options

   In the root directory of each branch matches this behavior. Options B, C, and D do not reflect the automatic per-branch Jenkinsfile usage.

3. Final Answer:

   In the root directory of each branch -> Option C

4. Quick Check:

   Jenkinsfile location = root of each branch [OK]

Hint: Jenkinsfile must be in branch root for multi-branch jobs [OK]

Common Mistakes:

• Thinking Jenkinsfile is centralized outside branches
• Assuming only main branch Jenkinsfile is used
• Believing Jenkinsfile is stored on Jenkins server

3. Given a multi-branch pipeline job configured to scan a Git repository with branches main and feature1, what happens when a new branch feature2 is pushed?

medium

A. The job automatically detects feature2 and creates a new pipeline for it

B. The job ignores feature2 until manually added

C. The job deletes pipelines for main and feature1

D. The job merges feature2 into main automatically

Solution

1. Step 1: Understand scan trigger behavior

   Multi-branch pipeline jobs scan the repository and detect new branches automatically, creating pipelines for them.

2. Step 2: Analyze options

   The job automatically detects feature2 and creates a new pipeline for it correctly states the automatic detection and pipeline creation for feature2. Options A, B, and D describe incorrect behaviors.

3. Final Answer:

   The job automatically detects feature2 and creates a new pipeline for it -> Option A

4. Quick Check:

   New branch detected = new pipeline created [OK]

Hint: New branches auto-create pipelines on scan [OK]

Common Mistakes:

• Assuming manual addition of new branches
• Thinking existing pipelines get deleted
• Confusing pipeline creation with branch merging

4. You created a multi-branch pipeline job but it does not detect any branches. What is the most likely cause?

medium

A. The Jenkinsfile is missing in the main branch only

B. The repository URL is incorrect or inaccessible

C. The Jenkins server is offline

D. The job is set to build only tags, not branches

Solution

1. Step 1: Check repository access

   If the multi-branch pipeline job cannot detect branches, the most common cause is an incorrect or inaccessible repository URL.

2. Step 2: Evaluate other options

   The Jenkinsfile is missing in the main branch only is less likely because missing Jenkinsfile in main branch does not prevent branch detection. The Jenkins server is offline is unrelated if Jenkins is running. The job is set to build only tags, not branches is possible but less common than repository access issues.

3. Final Answer:

   The repository URL is incorrect or inaccessible -> Option B

4. Quick Check:

   Branch detection fails if repo URL is wrong [OK]

Hint: Check repo URL first if no branches detected [OK]

Common Mistakes:

• Blaming missing Jenkinsfile for no branch detection
• Ignoring repository access permissions
• Assuming Jenkins server is offline without checking

5. You want to configure a multi-branch pipeline job to scan your GitHub repo every 15 minutes to detect new branches or changes. Which Jenkins feature should you use?

hard

A. Use a freestyle job to poll the repository

B. Manually run the scan from Jenkins dashboard each time

C. Configure a webhook in GitHub but disable Jenkins scanning

D. Set a periodic scan trigger with a cron expression like H/15 * * * *

Solution

1. Step 1: Identify scan trigger configuration

   Multi-branch pipeline jobs support periodic scanning using cron syntax to detect branch changes automatically.

2. Step 2: Analyze options

   Set a periodic scan trigger with a cron expression like H/15 * * * * correctly describes setting a periodic scan trigger with cron. Manually run the scan from Jenkins dashboard each time is manual, not automatic. Configure a webhook in GitHub but disable Jenkins scanning disables Jenkins scanning, so no detection. Use a freestyle job to poll the repository uses freestyle job, not multi-branch pipeline.

3. Final Answer:

   Set a periodic scan trigger with a cron expression like H/15 * * * * -> Option D

4. Quick Check:

   Periodic scan trigger = automatic branch updates [OK]

Hint: Use cron trigger for automatic branch scanning [OK]

Common Mistakes:

• Relying only on manual scans
• Disabling Jenkins scan but using webhooks only
• Using freestyle jobs instead of multi-branch pipelines