Branch selection and branch specifier in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins branch specifier syntax output

What is the output of the Jenkins branch specifier origin/feature/* when used in a Multibranch Pipeline job?

A Matches all branches named 'feature/*' from any remote.

B Matches only the branch literally named 'origin/feature/*'.

C Matches all branches starting with 'origin/feature/' from any remote.

D Matches all branches starting with 'feature/' from the remote named 'origin'.

💡 Hint

Think about how Jenkins interprets remote names and wildcards in branch specifiers.

The specifier origin/feature/* matches any branch under 'feature/' on the remote named 'origin'. It does not match branches literally named 'origin/feature/*' or branches from other remotes.

🧠 Conceptual

intermediate

Understanding Jenkins branch selection behavior

In Jenkins Multibranch Pipeline, what does the branch specifier */main select?

A Selects the 'main' branch from any remote repository.

B Selects all branches named 'main' only from the default remote.

C Selects branches named 'main' only from remotes named '*'.

D Selects all branches starting with 'main' from any remote.

💡 Hint

The asterisk (*) is a wildcard for remote names.

The */main specifier means 'any remote' (the asterisk) and the branch named 'main'. So it matches the 'main' branch from all remotes.

❓ Troubleshoot

advanced

Troubleshooting branch not detected in Jenkins

A Jenkins Multibranch Pipeline job does not detect the branch feature/login even though it exists in the remote repository. The branch specifier is set to origin/feature/*. What is the most likely cause?

A The branch specifier should be <code>feature/*</code> without the remote prefix.

B The remote name 'origin' is incorrect or not configured in Jenkins.

C The branch specifier must be <code>refs/heads/feature/*</code> to detect branches.

D The Jenkins job requires a manual refresh to detect new branches.

💡 Hint

Check the remote repository configuration in Jenkins.

If the remote name 'origin' is not configured or mismatched, Jenkins cannot find branches under that remote. The specifier depends on the remote name being correct.

🔀 Workflow

advanced

Configuring Jenkins to build only specific branches

You want Jenkins Multibranch Pipeline to build only the branches main and any branch starting with release/. Which branch specifier configuration achieves this?

A Use a single branch specifier: <code>refs/heads/main refs/heads/release/*</code>.

B Use a single branch specifier: <code>main, release/*</code>.

C Use two branch specifiers: <code>*/main</code> and <code>*/release/*</code>.

D Use a single branch specifier: <code>main|release/*</code>.

💡 Hint

Jenkins allows multiple branch specifiers separated by commas or multiple entries.

Jenkins Multibranch Pipeline supports multiple branch specifiers by listing them separately. Using */main and */release/* matches the main branch and all release branches.

✅ Best Practice

expert

Best practice for branch specifier in Jenkins Multibranch Pipeline

What is the best practice for writing branch specifiers in Jenkins Multibranch Pipeline to ensure consistent branch detection across different remotes?

A Always use <code>*/branch-name</code> to match the branch on any remote.

B Always use <code>origin/branch-name</code> to specify the default remote explicitly.

C Use full refspecs like <code>refs/remotes/origin/branch-name</code> for clarity.

D Use only branch names without remote prefixes, like <code>branch-name</code>.

💡 Hint

Consider flexibility when remotes may vary.

Using */branch-name allows Jenkins to detect the branch regardless of the remote name, making the configuration more flexible and less error-prone.

Practice

1. What does the Branch Specifier field in Jenkins do?

easy

A. It tells Jenkins which branch or branches to build.

B. It specifies the build timeout duration.

C. It defines the build environment variables.

D. It sets the Jenkins user permissions.

Solution

1. Step 1: Understand the purpose of Branch Specifier

   The Branch Specifier is used to tell Jenkins which branch or branches to build from the source code repository.

2. Step 2: Eliminate unrelated options

   Timeout, environment variables, and user permissions are unrelated to branch selection.

3. Final Answer:

   It tells Jenkins which branch or branches to build. -> Option A

4. Quick Check:

   Branch Specifier = Select branch to build [OK]

Hint: Branch Specifier selects branches to build in Jenkins [OK]

Common Mistakes:

• Confusing branch specifier with build timeout
• Thinking it sets environment variables
• Assuming it controls user permissions

2. Which of the following is the correct syntax to specify the master branch in Jenkins Branch Specifier?

easy

A. refs/remotes/master

B. refs/tags/master

C. refs/heads/master

D. refs/branches/master

Solution

1. Step 1: Recall Git reference format for branches

   Branches in Git are referenced as refs/heads/branch-name. So the master branch is refs/heads/master.

2. Step 2: Identify incorrect references

   refs/tags/ is for tags, refs/remotes/ is for remote tracking branches, and refs/branches/ is not a valid Git ref.

3. Final Answer:

   refs/heads/master -> Option C

4. Quick Check:

   Branch refs start with refs/heads/ [OK]

Hint: Use refs/heads/branch-name for branch specifier [OK]

Common Mistakes:

• Using refs/tags/ instead of refs/heads/
• Confusing remote refs with local branch refs
• Using invalid refs/branches/ prefix

3. Given the branch specifier refs/heads/feature/*, which branches will Jenkins build?

medium

A. Only the branch named exactly 'feature/*'.

B. Only the 'master' branch.

C. All branches except those starting with 'feature/'.

D. All branches starting with 'feature/', like 'feature/login' and 'feature/ui'.

Solution

1. Step 1: Understand wildcard usage in branch specifier

   The asterisk (*) acts as a wildcard matching any characters after 'feature/'. So it matches all branches starting with 'feature/'.

2. Step 2: Analyze each option

   Only the branch named exactly 'feature/*'. is incorrect because it treats '*' literally. All branches except those starting with 'feature/'. is opposite meaning. Only the 'master' branch. is unrelated.

3. Final Answer:

   All branches starting with 'feature/', like 'feature/login' and 'feature/ui'. -> Option D

4. Quick Check:

   Wildcard * matches multiple branches [OK]

Hint: Use * wildcard to match multiple branches [OK]

Common Mistakes:

• Treating * as a literal character
• Assuming it excludes matching branches
• Confusing branch names with tags

4. You set the branch specifier to refs/heads/release but Jenkins builds no branches. What is the likely problem?

medium

A. The branch name is incorrect or does not exist in the repo.

B. The Jenkins server is offline.

C. The build script has syntax errors.

D. The workspace is full.

Solution

1. Step 1: Check branch existence

   If Jenkins builds no branches, the specified branch refs/heads/release might not exist in the repository.

2. Step 2: Rule out unrelated issues

   Server offline, build script errors, or workspace full would cause different errors or failures, not silent no build.

3. Final Answer:

   The branch name is incorrect or does not exist in the repo. -> Option A

4. Quick Check:

   Branch specifier must match existing branch [OK]

Hint: Verify branch exists before setting specifier [OK]

Common Mistakes:

• Assuming Jenkins server status causes no build
• Blaming build script syntax for branch selection
• Ignoring branch existence check

5. You want Jenkins to build all branches except those starting with hotfix/. Which branch specifier pattern should you use?

hard

A. !refs/heads/*

B. refs/heads/*, !refs/heads/hotfix/*

C. refs/heads/*

D. refs/heads/hotfix/*

Solution

1. Step 1: Understand inclusion and exclusion patterns

   Jenkins supports including all branches with refs/heads/* and excluding specific branches with !refs/heads/hotfix/*.

2. Step 2: Analyze options

   refs/heads/*, !refs/heads/hotfix/* includes all branches but excludes hotfix branches. refs/heads/hotfix/* only includes hotfix branches. refs/heads/* includes all branches without exclusion. !refs/heads/* excludes all branches.

3. Final Answer:

   refs/heads/*, !refs/heads/hotfix/* -> Option B

4. Quick Check:

   Use ! to exclude branches in specifier [OK]

Hint: Use ! prefix to exclude branches in specifier [OK]

Common Mistakes:

• Not using exclusion pattern with !
• Only specifying excluded branches
• Excluding all branches accidentally