Branch indexing and scanning in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What happens during branch indexing in Jenkins Multibranch Pipeline?

In Jenkins Multibranch Pipeline, what is the main purpose of branch indexing?

A It runs all the builds for every branch found in the repository.

B It deletes old build artifacts from all branches to save disk space.

C It scans the source repository to discover branches and creates jobs for each branch.

D It merges all branches into the main branch automatically.

💡 Hint

Think about what Jenkins needs to do before it can build branches.

Branch indexing scans the source repository to find branches and creates Jenkins jobs for each branch so they can be built separately.

💻 Command Output

intermediate

Output of branch indexing scan log in Jenkins

What output would you expect to see in Jenkins logs after a successful branch indexing scan?

Jenkins

Started branch indexing
Found branches: feature1, bugfix2
Created jobs for branches
Finished branch indexing

A Deleted old branches\nCleaned workspace

B Error: No branches found\nBranch indexing aborted

C Started build for branch feature1\nBuild successful

D Started branch indexing\nFound branches: feature1, bugfix2\nCreated jobs for branches\nFinished branch indexing

💡 Hint

Look for messages about scanning and job creation, not building or errors.

The branch indexing log shows scanning started, branches found, jobs created, and indexing finished.

❓ Configuration

advanced

Configuring branch indexing frequency in Jenkins Multibranch Pipeline

Which configuration snippet correctly sets branch indexing to run every 15 minutes in a Jenkinsfile?

A properties([pipelineTriggers([cron('H/15 * * * *')])])

B triggers { cron('*/15 * * * *') }

C options { timeout(time: 15, unit: 'MINUTES') }

D pipeline { triggers { pollSCM('H/15 * * * *') } }

💡 Hint

Branch indexing frequency is set via pipeline triggers with cron syntax.

Using properties([pipelineTriggers([cron('H/15 * * * *')])]) sets the branch indexing to run every 15 minutes.

❓ Troubleshoot

advanced

Why does Jenkins fail to detect new branches during indexing?

After adding new branches to the repository, Jenkins Multibranch Pipeline does not detect them during branch indexing. What is a likely cause?

A The Jenkinsfile in the new branches contains syntax errors.

B The repository credentials used by Jenkins lack read permission for the new branches.

C The build triggers are set to manual only.

D The Jenkins server is running out of disk space.

💡 Hint

Think about access rights Jenkins needs to see branches.

If Jenkins cannot read the new branches due to credential permission issues, it will not detect them during indexing.

🔀 Workflow

expert

Order the steps Jenkins performs during branch indexing and scanning

Put the following Jenkins branch indexing steps in the correct order.

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 3,1,2,4

💡 Hint

Think about discovery first, then job creation, then triggers, then finishing.

Jenkins first scans the repo, creates or updates jobs, runs triggers, then finishes indexing.