Pull request builds in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkinsfile snippet output for pull request build trigger

Given this Jenkinsfile snippet, what will be the output when a pull request is created?

pipeline {
  agent any
  triggers {
    githubPullRequest()
  }
  stages {
    stage('Build') {
      steps {
        echo "Building PR #${env.CHANGE_ID}"
      }
    }
  }
}

Jenkins

pipeline {
  agent any
  triggers {
    githubPullRequest()
  }
  stages {
    stage('Build') {
      steps {
        echo "Building PR #${env.CHANGE_ID}"
      }
    }
  }
}

A Build stage skipped

B Building PR #null

C Building PR #0

D Building PR #42

💡 Hint

The environment variable CHANGE_ID contains the pull request number during PR builds.

The githubPullRequest trigger sets environment variables like CHANGE_ID to the PR number. The echo prints this number.

❓ Configuration

intermediate

Correct Jenkinsfile stage condition for PR builds

Which Jenkinsfile stage condition correctly runs the stage only for pull request builds?

A when { changeRequest() }

B when { branch 'main' }

C when { environment name: 'CHANGE_ID', value: '' }

D when { not { changeRequest() } }

💡 Hint

Use the built-in condition to detect pull request builds.

The 'changeRequest()' condition runs the stage only if the build is triggered by a pull request.

❓ Troubleshoot

advanced

Why does the Jenkins pull request build not trigger?

A Jenkins pipeline with 'githubPullRequest()' trigger does not start when a pull request is created. What is the most likely cause?

A GitHub webhook for pull requests is not configured or missing

B The Jenkinsfile syntax is invalid

C The Jenkins agent is offline

D The repository has no branches

💡 Hint

Check if GitHub is notifying Jenkins about pull request events.

The 'githubPullRequest()' trigger relies on GitHub webhooks to notify Jenkins of PR events. Without the webhook, builds won't start.

🔀 Workflow

advanced

Order of steps in a Jenkins pull request build workflow

Arrange the steps in the correct order for a Jenkins pipeline triggered by a pull request.

A 1,3,2,4

B 2,1,3,4

C 1,2,3,4

D 3,1,2,4

💡 Hint

Think about event flow from GitHub to Jenkins and back.

GitHub sends the event first, Jenkins triggers the pipeline, pipeline runs stages, then results are reported back.

✅ Best Practice

expert

Best practice for securing Jenkins pull request builds

Which practice best secures Jenkins pull request builds against malicious code in PRs?

A Disable pull request builds to avoid risk

B Run PR builds in isolated containers with limited permissions

C Run PR builds with full admin privileges

D Allow PR builds to run on the main Jenkins master node

💡 Hint

Think about isolating untrusted code.

Running PR builds in isolated containers limits damage from malicious code and protects the Jenkins environment.

Practice

1. What is the main purpose of pull request builds in Jenkins?

easy

A. To automatically test code changes before merging

B. To deploy code directly to production

C. To delete old branches after merging

D. To manually review code without testing

Solution

1. Step 1: Understand pull request builds concept

   Pull request builds run tests automatically on code changes before merging to ensure quality.

2. Step 2: Compare options with purpose

   Only To automatically test code changes before merging describes automatic testing before merging, which is the main goal.

3. Final Answer:

   To automatically test code changes before merging -> Option A

4. Quick Check:

   Pull request builds = automatic pre-merge tests [OK]

Hint: Pull request builds test code before merging [OK]

Common Mistakes:

• Confusing deployment with testing
• Thinking pull request builds delete branches
• Assuming manual review replaces automated tests

2. Which Jenkins pipeline syntax correctly triggers a build on a GitHub pull request?

easy

A. triggers { githubPush() }

B. triggers { cron('H/5 * * * *') }

C. triggers { githubPullRequest() }

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

Solution

1. Step 1: Identify trigger for pull request builds

   The correct trigger for GitHub pull request builds in Jenkins is githubPullRequest().

2. Step 2: Eliminate other triggers

   githubPush() triggers on push events, cron and pollSCM are time-based triggers, not pull request triggers.

3. Final Answer:

   triggers { githubPullRequest() } -> Option C

4. Quick Check:

   Pull request trigger = githubPullRequest() [OK]

Hint: Use githubPullRequest() for PR triggers [OK]

Common Mistakes:

• Using githubPush() instead of githubPullRequest()
• Confusing time-based triggers with PR triggers
• Omitting triggers block entirely

3. Given this Jenkinsfile snippet, what happens when a pull request is opened?

pipeline {
  agent any
  triggers {
    githubPullRequest()
  }
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
  }
}

medium

A. The pipeline waits for manual approval before running

B. The pipeline runs automatically and prints 'Building...'

C. The pipeline runs only on push events, not pull requests

D. The pipeline fails due to syntax error

Solution

1. Step 1: Analyze trigger block

   The trigger githubPullRequest() starts the pipeline automatically on pull request events.

2. Step 2: Check pipeline steps

   The pipeline has a 'Build' stage that echoes 'Building...'. No manual approval or syntax errors are present.

3. Final Answer:

   The pipeline runs automatically and prints 'Building...' -> Option B

4. Quick Check:

   githubPullRequest() triggers automatic build [OK]

Hint: githubPullRequest() triggers auto build on PR [OK]

Common Mistakes:

• Assuming manual approval is needed
• Confusing push and pull request triggers
• Thinking syntax error exists in snippet

4. A Jenkins pipeline with githubPullRequest() trigger does not start when a pull request is created. What is the most likely cause?

medium

A. The GitHub webhook for pull requests is not configured

B. The Jenkinsfile has a syntax error in the stages block

C. The pipeline uses cron trigger instead

D. The pull request was merged before the build started

Solution

1. Step 1: Understand trigger requirements

   The githubPullRequest() trigger requires GitHub webhooks to notify Jenkins of PR events.

2. Step 2: Identify common failure reason

   If the webhook is missing or misconfigured, Jenkins won't start the build on PR creation.

3. Final Answer:

   The GitHub webhook for pull requests is not configured -> Option A

4. Quick Check:

   Missing webhook = no PR build trigger [OK]

Hint: Check GitHub webhook setup if PR builds don't start [OK]

Common Mistakes:

• Blaming syntax errors without checking webhooks
• Ignoring webhook configuration
• Assuming cron triggers handle PR events

5. You want Jenkins to build pull requests only from specific branches (e.g., 'feature/*') and skip others. Which configuration snippet achieves this?

hard

A. triggers { githubPullRequest { branchFilter { exclude 'feature/*' } } }

B. triggers { pollSCM { ignoreBranches 'feature/*' } }

C. triggers { githubPush { branch 'feature/*' } }

D. triggers { githubPullRequest { branchFilter { include 'feature/*' } } }

Solution

1. Step 1: Identify correct trigger and filter syntax

   The githubPullRequest trigger supports branchFilter with include to specify branches to build.

2. Step 2: Compare options for filtering

   triggers { githubPullRequest { branchFilter { include 'feature/*' } } } includes only 'feature/*' branches, which matches the requirement. triggers { githubPullRequest { branchFilter { exclude 'feature/*' } } } excludes them, which is opposite. Options C and D use wrong triggers or syntax.

3. Final Answer:

   triggers { githubPullRequest { branchFilter { include 'feature/*' } } } -> Option D

4. Quick Check:

   Use branchFilter include to limit PR builds [OK]

Hint: Use branchFilter include to build specific PR branches [OK]

Common Mistakes:

• Using exclude instead of include
• Using githubPush instead of githubPullRequest
• Trying to filter branches with pollSCM