Branch indexing and scanning in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is branch indexing in Jenkins?

Branch indexing is the process Jenkins uses to discover all branches in a source code repository so it can create or update jobs for each branch automatically.

beginner

What does branch scanning do in Jenkins Multibranch Pipeline?

Branch scanning checks the repository for new, changed, or deleted branches and updates Jenkins jobs accordingly to keep builds in sync with the repository.

intermediate

How often does Jenkins perform branch indexing by default?

By default, Jenkins performs branch indexing every 1 hour, but this interval can be configured in the Multibranch Pipeline settings.

beginner

Why is branch indexing important in Jenkins Multibranch Pipelines?

It ensures Jenkins automatically detects new branches and removes deleted ones, so builds stay up-to-date without manual job creation or deletion.

intermediate

What happens if branch scanning is disabled in Jenkins?

If branch scanning is disabled, Jenkins will not detect new or deleted branches automatically, requiring manual job management for branches.

What is the main purpose of branch indexing in Jenkins?

A To discover and manage branches automatically

B To build Docker images

C To deploy applications to production

D To monitor server health

Branch indexing helps Jenkins find all branches in the repository and manage jobs for them automatically.

How does Jenkins know when to update branch jobs in a Multibranch Pipeline?

A By checking disk space

B By manual user input only

C By monitoring CPU usage

D By performing branch scanning at set intervals

Jenkins uses branch scanning to check for new, changed, or deleted branches and updates jobs accordingly.

What happens if a branch is deleted in the repository but branch scanning is not run?

A Jenkins automatically deletes the job

B Jenkins crashes

C The Jenkins job for that branch remains until manually deleted

D The branch is restored in the repository

Without branch scanning, Jenkins does not detect deleted branches and their jobs remain until manually removed.

Which Jenkins feature automatically creates jobs for new branches?

A Branch indexing

B Build triggers

C Post-build actions

D Pipeline script

Branch indexing discovers new branches and creates jobs for them automatically.

Can the frequency of branch indexing be changed in Jenkins?

A Only by editing Jenkins core files

B Yes, it can be configured in the Multibranch Pipeline settings

C No, it is fixed and cannot be changed

D Only by reinstalling Jenkins

Jenkins allows configuring the interval for branch indexing in the Multibranch Pipeline job settings.

Explain how branch indexing and scanning help automate Jenkins Multibranch Pipelines.

Think about how Jenkins stays updated with changes in your source code branches.

Describe what could happen if branch scanning is disabled in a Jenkins Multibranch Pipeline project.

Consider the impact on automation and maintenance.