Branch selection and branch specifier in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the branch named 'main' in a Jenkins pipeline.

Jenkins

git branch: '[1]'

Drag options to blanks, or click blank then click option'

Amaster

Bdevelop

Cmain

Dfeature

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'master' when the repository uses 'main' as the default branch.

Leaving the branch name empty.

The branch specifier 'main' tells Jenkins to use the main branch for the build.

2fill in blank

medium

Complete the code to select the branch named 'feature-xyz' in a Jenkins pipeline.

Jenkins

git branch: '[1]'

Drag options to blanks, or click blank then click option'

Afeature-xyz

Brelease

Chotfix

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using a branch name that does not exist in the repository.

Using 'main' instead of the feature branch.

Specifying 'feature-xyz' selects that specific feature branch for the build.

3fill in blank

hard

Fix the error in the branch specifier to correctly select the 'develop' branch.

Jenkins

git branch: '[1]'

Drag options to blanks, or click blank then click option'

Adevelop

BDevelop

Cdev

Ddevelopment

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase 'Develop' instead of lowercase 'develop'.

Using a similar but incorrect branch name like 'dev'.

The branch name is case-sensitive. 'develop' is the correct lowercase branch name.

4fill in blank

hard

Fill both blanks to specify the branch and the repository URL in a Jenkins pipeline.

Jenkins

git url: '[1]', branch: '[2]'

Drag options to blanks, or click blank then click option'

Ahttps://github.com/example/repo.git

Bmain

Cdevelop

Dhttps://github.com/example/other.git

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up repository URLs.

Using the wrong branch name.

The URL points to the repository, and the branch specifies which branch to build.

5fill in blank

hard

Fill all three blanks to specify the repository URL, branch, and credentials ID in a Jenkins pipeline.

Jenkins

git url: '[1]', branch: '[2]', credentialsId: '[3]'

Drag options to blanks, or click blank then click option'

Ahttps://github.com/example/project.git

Bfeature-branch

Cgithub-credentials

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting credentials for private repositories.

Using the wrong branch or URL.

The URL is the repository location, the branch is the target branch, and credentialsId is used for authentication.

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