Skip to main content

Configure Build Trigger in Jenkin

To configure build triggers in Jenkins to be triggered when changes are pushed to a GitHub repository, you can follow these steps:

  1. Access Jenkins:
    • Open your Jenkins dashboard in a web browser.
  2. Navigate to Your Project:
    • Click on the name of the project (Freestyle project) you want to configure.
  3. Configure Build Triggers:
    1. In the project configuration, scroll down to the section labeled "Build Triggers."
  4. Check the Option "GitHub Hook Trigger for GITScm polling":
    • Check the box next to "GitHub Hook Trigger for GITScm polling." This option tells Jenkins to listen for GitHub webhook events and trigger builds when changes are pushed to the repository.
  5. Save Configuration:
    • Scroll down and click the "Save" or "Apply" button to save your project's configuration changes.
  6. Configure GitHub Webhook:
    • Now you need to set up a webhook in your GitHub repository to notify Jenkins about repository events.
    • Go to your GitHub repository.
    • Click on "Settings" at the top-right corner.
    • Navigate to "Webhooks" or "Webhooks & Services."
    • Click "Add webhook" or similar.
    • In the Payload URL, provide the URL of your Jenkins server's webhook endpoint. It usually looks like http://jenkins-server/github-webhook/.
    • Select "application/json" as the content type.
    • Choose the events that should trigger the webhook (e.g., "Push" events).
    • Save the webhook.
  7. Test the Trigger:
    • Make a small change to a file in your GitHub repository.
    • Push the change to GitHub.
    • Check your Jenkins project's build history. You should see a new build triggered by the webhook.
Please note that the exact steps and options might vary depending on your Jenkins version and configuration. Make sure your Jenkins server is accessible from the internet or your GitHub webhook configuration may fail to reach your Jenkins server.

Also, ensure you have configured proper security measures, as opening your Jenkins server to webhooks can be a security risk if not done correctly.

Comments

Popular posts from this blog

Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server

  Experiment No. 5 Title: Applying CI/CD Principles to Web Development Using Jenkins, Git, and Local HTTP Server  Objective: The objective of this experiment is to set up a CI/CD pipeline for a web development project using Jenkins, Git, and webhooks, without the need for a Jenkinsfile. You will learn how to automatically build and deploy a web application to a local HTTP server whenever changes are pushed to the Git repository, using Jenkins' "Execute Shell" build step. Introduction: Continuous Integration and Continuous Deployment (CI/CD) is a critical practice in modern software development, allowing teams to automate the building, testing, and deployment of applications. This process ensures that software updates are consistently and reliably delivered to end-users, leading to improved development efficiency and product quality. In this context, this introduction sets the stage for an exploration of how to apply CI/CD principles specifically to web development using J

Experiment No. 6 Title: Exploring Containerization and Application Deployment with Docker

  Experiment No. 6 Title: Exploring Containerization and Application Deployment with Docker  Objective: The objective of this experiment is to provide hands-on experience with Docker containerization and application deployment by deploying an Apache web server in a Docker container. By the end of this experiment, you will understand the basics of Docker, how to create Docker containers, and how to deploy a simple web server application. Introduction Containerization is a technology that has revolutionised the way applications are developed, deployed, and managed in the modern IT landscape. It provides a standardised and efficient way to package, distribute, and run software applications and their dependencies in isolated environments called containers. Containerization technology has gained immense popularity, with Docker being one of the most well-known containerization platforms. This introduction explores the fundamental concepts of containerization, its benefits, and how it differs

Experiment No. 10 Title: Create the GitHub Account to demonstrate CI/CD pipeline using Cloud Platform.

  Experiment No. 10 Title: Create the GitHub Account to demonstrate CI/CD pipeline using Cloud Platform. Objective: The objective of this experiment is to help you create a GitHub account and set up a basic CI/CD pipeline on GCP. You will learn how to connect your GitHub repository to GCP, configure CI/CD using Cloud Build, and automatically deploy web pages to an Apache web server when code is pushed to your repository. Introduction: Continuous Integration and Continuous Deployment (CI/CD) pipelines are essential for automating the deployment of web applications. In this experiment, we will guide you through creating a GitHub account and setting up a basic CI/CD pipeline using Google Cloud Platform (GCP) to copy web pages for an Apache HTTP web application. Continuous Integration and Continuous Deployment (CI/CD) is a crucial practice in modern software development. It involves automating the processes of code integration, testing, and deployment to ensure that software changes are co