Scribd
Upload
10 views3 pages

Jenkins - Continuous Integration Tool

Jenkins is a continuous integration tool that automates the software development life cycle (SDLC) by building, testing, and deploying code efficiently. It supports continuous integration, delivery, and deployment, allowing developers to identify errors quickly and improve delivery speed. The setup process involves downloading Jenkins, installing Java, and configuring the service on a server.

Uploaded by

Rakesh Mirchi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views3 pages

Jenkins - Continuous Integration Tool

Jenkins is a continuous integration tool that automates the software development life cycle (SDLC) by building, testing, and deploying code efficiently. It supports continuous integration, delivery, and deployment, allowing developers to identify errors quickly and improve delivery speed. The setup process involves downloading Jenkins, installing Java, and configuring the service on a server.

Uploaded by

Rakesh Mirchi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Jenkins ---> Continuous Integration Tool

Continuous Integration: The process to Build the code every time a developer pushes to the
repository and Test the code in a single server.

Advantages of Jenkins:

1.Errors can be found easily

2.We could know the successful integration of the code.

3.Speed Delivery.

4.Developers can be more efficient.

Continuous Delivery: Making ready for the Deployment.

Manual Intervention is need in continuous Delivery.

Continuous Deployment: It is the process of build, test and deploy to the production servers
without any manual intervention.

Continuous Integration Life Cycle:

Build ---> Test--->Deploy to staging --->Acceptance Test ---> Deploy to Production ---> Smoke Test

CI/CD Pipeline:

Version Control ⟶ Build ---> Unit Test ---> Deploy ---> Automation Test ---> Deploy to Production

And from there the Production FeedBack is being valutated and the process continuous.

Unit Test: In This we test the components of the code like structure, Dependencies, Format etc.

Automation Test: In this we test the actual performance. Which is as per the Client's requirement or
not.

The Deployment before the production deployment is called Pre-Production/Nonproduction


Deployment.

Jenkins is an open source which contains Plugins which will helps to automate the entire SDLC
(Software Development life Cycle).

Jenkins is platform Independent.

Advantages:

1.Follows Master Slave architecture.


Master ------->Slave1, Slave2, Slave3

The master will instruct the slave to perform certain activities.

2.We can write our own plugins and can also use the community plugins.

3.If slaves are not available, the master will perform the activity by itself.

4.We will come to what exactly is happening.

Jenkins Setup:

Step-1: Go to https://www.jenkins.io/download/.

Search for Red Hat Linux,

Copy paste the following

sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo

sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io-2023.key.

Step-2: Install Java (11 Version).

amazon-linux-extras install java-openjdk11 -y (For Amazon AMI)

yum install fontconfig java-11-openjdk ( For other flavors of Linux).

Step-3: Install Jenkins.

yum install jenkins -y

Step-4: Check whether the jenkins service is running or not.

systemctl status jenkins ---> gives the status of the jenkins.

systemctl start jenkins ----> Start the jenkins service.

Step-5: Connect to jenkins dashboard.

ip address:8080 in the web browser.

Continue with the installation of the jenkins.

You might also like