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.