Jenkins CI/CD Integration With Katalon: Step-by-Step Setup Guide

DevOps significantly changed the software industry. From a siloed summons where the focus was entirely order on development, leave little to no time to properly test it, to a combination of the two, simultaneously developing try to shorten the cycle. CI/CD is the key to that innovation, and Jenkins is & nbsp;on the market.
 

We ’ ll learn how to do Continuous Integration with Jenkins in this step-by-step guide.
 

What is DevOps?

DevOps is a development philosophy combining Development (Dev) and Operations (Ops) team to break down silos between them.
 

• Dev team & nbsp;is creditworthy for the coding, scripting, and integrate all of the part involve to make and run the application.
• Operations squad & nbsp;is responsible for the provision and direction of the infrastructure necessary for development. They also automate deployment pipelines to ensure that application deployments are consistent.
   

DevOps is possible thanks to the CI/CD pipeline.

What is CI/CD?

At its essence, CI/CD is about oftentimes building, examination, and integrating little code changes into a shared depository. This coming allows QA squad to test faster, earlier, along with development instead of & nbsp;afterdevelopment.
 

• Continuous Integration (CI) is the practice of committing code into a shared repository several times a day. Each commit triggers an automated build process to compile the code and & nbsp;.
• Uninterrupted Delivery (CD) is the next phase after CI where the software is delivered to product or scaffolding surround

What is Jenkins?

Jenkins is an open-source mechanisation server wide used for CI/CD pipelines. It allows QA team to automate the build, test, and deployment process of their package applications.

Jenkins is highly extensible and indorse integration with a wide range of plugins to facilitate users customize its functionality to fit their specific need.
 

This flexibility and simple-to-use nature makes Jenkins a perfect fit for building a CI/CD pipeline.
 

Jenkins Continuous Integration Tutorial

1. Prerequisites

To build a CI/CD line from Jenkins, you first need:
 

1. Java Development Kit
2. Knowledge to execute some introductory Linux commands

2. What To Do

First, & nbsp;download Jenkins. Read through the guide and choose the suitable package for your needs.
 

After that, open up a depot. Enter cd & lt; your-download-directory & gt;
 

For example, if you have your jenkins.war file inUsers/Downloads/Jenkinspamphlet, entercd Users/Downloads/Jenkins
 

Next, run this command:java -jar jenkins.war
 

The Terminal should generate this announcement.
 

Open your browser and navigate to & nbsp;http: //localhost:8080. This is when the Jenkins dashboard appears. Paste your password in to arrive at the Jenkins customization screen.
 

Once you have set up everything, you should arrive at the Jenkins Dashboard. Click “ Create a job ” to start.

After that, select the character of projection you desire to create. In this case, let ’ s go with the & nbsp;Pipeline & nbsp;option.

Upon redirection, the configuration page will be displayed.
 

Let ’ s see what each option is about:
 

After that, you ’ ll likewise see the & nbsp;Pipeline & nbsp;section. You can define different degree of your pipeline, such as check, build, test, deploy, etc. Each point represent a logical grouping of tasks within your pipeline. You likewise receive entire control over the logic and flow of your pipeline.
 

Here is a sample Pipeline handwriting:
 

pipeline {& nbsp; & nbsp; & nbsp; agent any & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; stages {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; stage ('Build ') {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; measure {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; // Checkout beginning code from Git repository & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; git 'https: //github.com/example/my-project.git' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; // Build the project using Maven & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; sh 'mvn clean package' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; phase ('Test ') {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; steps {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; // Run unit tests & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; sh 'mvn test' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; stage ('Deploy ') {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; measure {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; // Deploy the application to a test environs & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; sh 'kubectl apply -f deployment.yaml' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; post {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; success {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; // Send a notification on success & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; echo 'Pipeline executed successfully! ' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; failure {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; // Send a notification on failure & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; echo 'Pipeline execution failed! ' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp;}}

This script is a basic CI/CD line that checks out germ code from a Git repository, builds the projection habituate Maven, runs unit tests, and deploys the coating to a test surroundings.
 

Once done, you can click on the & nbsp;Build Now & nbsp;option to run the pipeline and check if it ’ s successful or not.
 

You can see the outcome of the pipeline in the level perspective.
 

Integrating Katalon With Jenkins CI

Jenkins support a blanket range of consolidation. Once you integrate Katalon with Jenkins, you get the best of both worlds.
 

Katalon offers comprehensive testing, allowing you to test website, desktop, API, and yet wandering coating quicker, best, and smarter with the help of AI-powered features. Katalon gives you everything you want to project, write tests, execute tests, manage tests, prepare tryout data, and generate reports. The rest you need is integrate it into your CI/CD pipeline. & nbsp;
 

See how you can make Katalon Studio playscript hither:
 

Once you have all the tests and integrated Katalon with Jenkins, you can execute Katalon Studio test in Jenkins with Jenkins Pipeline Script (Jenkinsfile).
 

On the Jenkins Dashboard, click on & nbsp;New Itemand make a new Jenkins Pipeline project. From the dropdown list, choose & nbsp;Pipeline Scriptas the undertaking type.

 

Copy and paste this command:
 

For Windows
 

grapevine {& nbsp; & nbsp; & nbsp; agent any & nbsp; & nbsp; & nbsp; stages {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; stage ('Test ') {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; step {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; bat `` '' '' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; cd & nbsp; & lt; KRE installed leaflet & gt; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; katalonc & nbsp; -projectPath= '' & lt; projectpath & gt; '' -browserType= '' & lt; browser & gt; '' -retry= & lt; number of retry times & gt; -statusDelay= & lt; seconds & gt; -testSuitePath= '' & lt; path & gt; '' -apiKey= '' & lt; user API key & gt; '' -orgID= & lt; Katalon_OrgID & gt; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; '' '' '' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp;}}

For MacOs

pipeline {& nbsp; & nbsp; & nbsp; agent any & nbsp; & nbsp; & nbsp; stages {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; level ('Test ') {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; steps {& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; sh `` ' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; cd & nbsp; & lt; KRE installed folder & gt; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; ./katalonc & nbsp; -projectPath= '' & lt; projectpath & gt; '' -browserType= '' & lt; browse & gt; '' -retry= & lt; number of retry clip & gt; -statusDelay= & lt; seconds & gt; -testSuitePath= '' & lt; path & gt; '' -apiKey= '' & lt; user API key & gt; '' -orgID= & lt; Katalon_OrgID & gt; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; '' ' & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;} & nbsp; & nbsp; & nbsp;}}

After that, click & nbsp;Save & nbsp;and click & nbsp;Build Now & nbsp;to run the project.