Jenkins - Creating pipeline and configuring Git Webhook for build trigger

For Jenkins Installation, refer: http://blog.rajaravi.com/2019/09/jenkins-installation.html

For Jenkins Pipeline definition, refer: http://blog.rajaravi.com/2019/09/jenkins-pipeline-methods-to-define.html

In this post, you can expect to learn Creating pipeline, Adding Git Webhook, Configuring pipeline build to be triggered automatically whenever code check-in happens in the Git repository

I'm using a sample GitHub repository to explain the software build along with a local Jenkins server for pipeline.

GitHub Repository: https://github.com/rrajaravi/anyserv
Jenkins Server: http://jenkins-server:8080/

Let us look at the Jenkins Pipeline creation for continuous delivery of the software anyserv

• In Jenkins click on "New Item"

• Enter an item name, click on "Pipeline" for the item type then click on "OK"

 

• In Build Triggers, Choose "GitHub hook trigger for GITScm polling"

• In Pipeline tab, choose "Pipeline script from SCM"

• After choosing Pipeline script from SCM, choose "Git" in SCM selection. Enter the Repository URL. By default Branch name is "master" and Pipeline script name is "Jenkinsfile", Customize it according to your requirement. Click on "Save"

• Pipeline is saved now and you can see the Pipeline window. There is no data in the Stage View because the Pipeline has not yet run. Click on Build Now to trigger the software build

• The build should be successful after few minutes. The Stage View would appear on the screen. Refresh the page to look at the Artifacts generated by the build. You can download the Artifact anyserv2.zip by clicking on it.

• As of now, we have triggered this software build manually. Let us configure GitHub Webhook to trigger this software build Automatically when ever a check in made to the repository

• Open the GitHub repository navigate to "Settings" --> "Webhooks" --> Click on "Add webhook"

• In "Payload URL" - Provide Jenkins URL along with github-webhook/ URI, I.e http://jenkins-server:8080/github-webhook/

          In "Content type" - Choose "application/json"

          In "Which events would you like to trigger this webhook?" - Select "Send me everything"

          then click on "Add Webhook"

• In Pipeline, Build Triggers - "GitHub hook trigger for GITScm polling" has been already chosen, hence it will allow the build to be triggered by GitHub hook
  
• Now performing a commit change in the Git repo would trigger the build automatically

• "GitHub Hook Log" option is available in the Pipeline window itself to see the Hook Log

By creating the Jenkins pipeline and GitHub Webhook, you can ensure the software build is triggered automatically for new code changes. The latest software is build by the pipeline and ready for usage all the time.