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.