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

Post a Comment

Popular posts from this blog

Example of Maven project that interacts with a MySQL database and includes testing

Example Maven project that interacts with a MySQL database and includes testing To install Java, MySQL, Maven, and write a Java program to fetch table data, execute, and create a JAR file using Maven on Ubuntu, you can follow these steps: Step 1: Install Java You can install Java using the following commands: sudo apt update sudo apt install default-jre sudo apt install default-jdk Verify the installation by running: java -version Step 2: Install MySQL You can install MySQL using the following commands: sudo apt update sudo apt install mysql-server During the installation, you'll be prompted to set a root password for MySQL or you can set password at latter stage using following steps.  sudo mysql ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'; exit Step 3: Install Maven You can install Maven using the following commands: sudo apt update sudo apt install maven Verify the installation by running: mvn -version Step 4: Create
Post a Comment
Read more

Maven Create and Build Artifacts

In Maven, you can create and build artifacts using the package phase of the build lifecycle. The package phase is responsible for taking the compiled code and other project resources and packaging them into a distributable format, such as a JAR (Java Archive), WAR (Web Application Archive), or other custom formats. Here are the steps to create and build artifacts using Maven: Configure the Build Output: In your project's pom.xml file, you need to configure the output of the build. This includes specifying the type of artifact you want to create (e.g., JAR, WAR) and any additional resources to include. You do this in the <build> section of your pom.xml: <build>     <finalName>my-artifact</finalName> <!-- Name of the artifact without the extension -->     <plugins>         <!-- Plugin configurations for creating the artifact -->         <!-- For example, maven-jar-plugin or maven-war-plugin -->     </plugins> </build> Depend
Post a Comment
Read more

Maven Repositories (local, central, global)

Maven relies on repositories to manage dependencies, plugins, and other artifacts required for a project. There are typically three types of repositories in Maven: local, central, and remote/global repositories. Local Repository: Location: The local repository is located on your local development machine. By default, it's in the .m2 directory within your user home directory (e.g., C:\Users\<username>\.m2\repository on Windows or /Users/<username>/.m2/repository on macOS and Linux). Purpose: The local repository is used to store artifacts (JARs, POMs, and other files) that your machine has downloaded or built during previous Maven builds. These artifacts are specific to your local development environment. Benefits: Using a local repository improves build performance since it caches dependencies locally, reducing the need to download them repeatedly. It also ensures reproducibility by maintaining a local copy of dependencies. Central Repository: Location: The central repo
Post a Comment
Read more