Pull request builds in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a pull request build in Jenkins?

A pull request build is a Jenkins job that automatically runs tests and checks on code changes submitted via a pull request before merging into the main branch.

beginner

Why are pull request builds important?

They help catch errors early by testing code changes before merging, ensuring the main codebase stays stable and reducing bugs in production.

intermediate

Which Jenkins plugin is commonly used to trigger builds on pull requests?

The 'GitHub Branch Source' plugin is commonly used to detect pull requests and trigger Jenkins builds automatically.

intermediate

How does Jenkins know which pull request to build?

Jenkins listens to webhook events from the source code repository (like GitHub) that notify it when a pull request is created or updated.

beginner

What is a common step in a pull request build pipeline?

Common steps include checking out the pull request code, running automated tests, performing static code analysis, and reporting results back to the pull request.

What triggers a pull request build in Jenkins?

A Scheduled daily at midnight

B Manual start by a developer only

C A webhook event from the source code repository

D When the main branch is updated

Jenkins uses webhook events from the repository to automatically trigger builds when pull requests are created or updated.

Which plugin helps Jenkins detect pull requests from GitHub?

A Email Extension

B GitHub Branch Source

C Docker Plugin

D Pipeline Utility Steps

The GitHub Branch Source plugin enables Jenkins to detect branches and pull requests from GitHub repositories.

What is the main benefit of running pull request builds?

A To test code changes before merging

B To deploy code to production

C To delete old branches

D To increase build time

Pull request builds test code changes early to prevent broken code from entering the main branch.

What does Jenkins typically do after a pull request build finishes?

A Reports the build status back to the pull request

B Deletes the pull request automatically

C Merges the pull request without review

D Sends an email to all users

Jenkins reports the build results back to the pull request so developers can see if tests passed or failed.

Which of these is NOT usually part of a pull request build pipeline?

A Running automated tests

B Checking out pull request code

C Static code analysis

D Manual code review by Jenkins

Manual code review is done by humans, not Jenkins. Jenkins automates testing and analysis.

Explain how Jenkins integrates with GitHub to run pull request builds.

Think about how Jenkins knows when a pull request is created or updated.

Describe the key steps in a typical pull request build pipeline in Jenkins.

Focus on what Jenkins does from start to finish during the build.