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.