Why Build triggers (poll SCM, webhook, timer) in Jenkins? - Purpose & Use Cases

The Big Idea

What if your builds could start themselves exactly when needed, without you doing anything?

The Scenario

Imagine you have a project where you need to build your code every time someone changes it. Without automation, you have to check the code repository yourself, then start the build manually each time.

The Problem

This manual checking is slow and tiring. You might forget to build after changes, causing delays and bugs. It's also easy to make mistakes or miss updates, which breaks the flow of work.

The Solution

Build triggers in Jenkins automatically start builds when something happens, like code changes or at set times. This means no more waiting or checking manually; the system does it for you instantly and reliably.

Before vs After

✗ Before

Check repo -> If changed, click 'Build' button

✓ After

Set trigger: poll SCM every 5 minutes or webhook on push

What It Enables

It lets your builds run automatically and instantly, keeping your project always up-to-date without lifting a finger.

Real Life Example

A team pushes code to GitHub, and Jenkins starts the build immediately via webhook, so everyone sees the latest tested version fast.

Key Takeaways

Manual builds cause delays and errors.

Build triggers automate starting builds on events.

This keeps projects fresh and developers focused on coding.

Practice

1. Which Jenkins build trigger checks the source code repository regularly for changes before starting a build?

easy

A. poll SCM

B. webhook

C. timer (cron)

D. manual trigger

Solution

1. Step 1: Understand the purpose of poll SCM

   poll SCM trigger makes Jenkins check the source code repository at set intervals for any changes.

2. Step 2: Compare with other triggers

   Webhook triggers build instantly on code push, timer triggers build at scheduled times, manual trigger requires user action.

3. Final Answer:

   poll SCM -> Option A

4. Quick Check:

   poll SCM = checks repo regularly [OK]

Hint: poll SCM means Jenkins checks repo regularly [OK]

Common Mistakes:

• Confusing webhook with poll SCM
• Thinking timer triggers check repo changes
• Assuming manual trigger is automatic

2. Which of the following is the correct syntax to schedule a Jenkins build every day at midnight using cron?

easy

A. * * * * 0

B. 0 0 * * *

C. 0 12 * * *

D. 0 0 0 * *

Solution

1. Step 1: Understand cron syntax

   Cron format is 'minute hour day month weekday'. To run at midnight daily, minute=0 and hour=0.

2. Step 2: Match the correct expression

   0 0 * * * "0 0 * * *" means every day at 00:00 hours (midnight).

3. Final Answer:

   0 0 * * * -> Option B

4. Quick Check:

   Midnight daily cron = 0 0 * * * [OK]

Hint: Midnight daily cron is always '0 0 * * *' [OK]

Common Mistakes:

• Mixing hour and minute fields
• Using wrong day or weekday values
• Confusing 12 PM with midnight

3. Given this Jenkins pipeline snippet, what will trigger the build?

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

medium

A. Build runs only if SCM changes detected every 15 minutes

B. Build runs every 15 minutes regardless of changes

C. Build runs once daily at 15 minutes past midnight

D. Build runs immediately after a webhook event

Solution

1. Step 1: Understand pollSCM with 'H/15 * * * *'

   This means Jenkins checks the SCM every 15 minutes for changes.

2. Step 2: Determine when build triggers

   Build triggers only if changes are detected during these checks, not every 15 minutes automatically.

3. Final Answer:

   Build runs only if SCM changes detected every 15 minutes -> Option A

4. Quick Check:

   pollSCM triggers on changes every 15 mins [OK]

Hint: pollSCM triggers only on changes, not just time [OK]

Common Mistakes:

• Assuming build runs every 15 minutes regardless
• Confusing pollSCM with timer trigger
• Thinking webhook triggers are involved here

4. A Jenkins job with this trigger configuration does not start builds as expected:

triggers {
  pollSCM('H/5 * * * *')
}

What is the most likely cause?

medium

A. Timer trigger conflicts with pollSCM

B. The cron syntax 'H/5 * * * *' is invalid

C. Webhook is required for pollSCM to work

D. SCM polling is disabled in Jenkins global settings

Solution

1. Step 1: Check pollSCM prerequisites

   pollSCM requires SCM polling enabled globally in Jenkins settings.

2. Step 2: Validate other options

   Syntax 'H/5 * * * *' is valid; webhook is separate trigger; no conflict with timer here.

3. Final Answer:

   SCM polling is disabled in Jenkins global settings -> Option D

4. Quick Check:

   pollSCM needs global SCM polling enabled [OK]

Hint: pollSCM needs global SCM polling enabled [OK]

Common Mistakes:

• Assuming cron syntax is wrong
• Thinking webhook is mandatory for pollSCM
• Believing timer conflicts cause failure

5. You want Jenkins to build your project automatically every weekday at 6 AM and also immediately when code is pushed to GitHub. Which trigger setup is best?

hard

A. Use only pollSCM with cron '0 6 * * 1-5'

B. Use webhook only without timer

C. Use timer trigger '0 6 * * 1-5' and configure GitHub webhook

D. Use pollSCM every minute

Solution

1. Step 1: Understand requirements

   Build at 6 AM weekdays and immediately on GitHub push means two triggers needed: timer and webhook.

2. Step 2: Evaluate options

   Use timer trigger '0 6 * * 1-5' and configure GitHub webhook combines timer for scheduled build and webhook for instant build on push, fulfilling both needs.

3. Final Answer:

   Use timer trigger '0 6 * * 1-5' and configure GitHub webhook -> Option C

4. Quick Check:

   Timer + webhook = scheduled + instant builds [OK]

Hint: Combine timer and webhook for schedule plus instant build [OK]

Common Mistakes:

• Using only pollSCM misses instant build
• Using webhook alone misses scheduled build
• Polling every minute is inefficient