Webhook triggers from GitHub/GitLab in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a webhook in the context of GitHub or GitLab?

A webhook is a way for GitHub or GitLab to send a message to another system, like Jenkins, when something happens in a repository, such as a code push or pull request.

beginner

How does Jenkins use webhooks from GitHub or GitLab?

Jenkins listens for webhook messages from GitHub or GitLab to automatically start a build or deployment when code changes are pushed.

beginner

What is the main benefit of using webhook triggers in Jenkins pipelines?

The main benefit is automation: Jenkins can start jobs immediately after code changes, saving time and reducing manual work.

intermediate

Which Jenkins plugin is commonly used to integrate GitHub webhooks?

The 'GitHub plugin' is commonly used to connect Jenkins with GitHub webhooks for triggering builds.

intermediate

What must you configure in GitHub or GitLab to enable webhook triggers for Jenkins?

You must set the webhook URL in the repository settings pointing to your Jenkins server's webhook endpoint and select which events trigger the webhook.

What event typically triggers a Jenkins build via a GitHub webhook?

A Changing the repository description

B A code push to the repository

C Opening a new issue

D Adding a new collaborator

A code push to the repository is the common event that triggers Jenkins builds via webhooks.

Which Jenkins plugin helps receive webhook calls from GitHub?

A Docker plugin

B Slack plugin

C GitHub plugin

D Pipeline plugin

The GitHub plugin allows Jenkins to receive webhook calls from GitHub.

Where do you configure the webhook URL in GitLab to trigger Jenkins?

A Repository Settings > Webhooks

B User Profile > Webhooks

C Group Settings > Integrations

D Project Wiki

Webhook URLs are configured in the repository settings under Webhooks.

What protocol does Jenkins use to receive webhook calls from GitHub/GitLab?

A HTTP/HTTPS

B FTP

C SSH

D SMTP

Webhooks use HTTP or HTTPS to send messages to Jenkins.

What is a common security measure when setting up webhooks for Jenkins?

A Using FTP for webhook delivery

B Allowing anonymous access to Jenkins

C Disabling SSL

D Using a secret token to verify webhook messages

A secret token helps Jenkins verify that webhook messages are from a trusted source.

Explain how webhook triggers from GitHub or GitLab automate Jenkins builds.

Think about what happens when you push code and how Jenkins knows to start.

Describe the steps to configure a webhook in GitHub to trigger a Jenkins job.

Focus on the GitHub side setup before Jenkins reacts.