Scribd
Upload
11 views11 pages

Jenkins Slides

Uploaded by

Lakshmi Narayana
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODP, PDF, TXT or read online on Scribd
11 views11 pages

Jenkins Slides

Uploaded by

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

Continuous Integration (CI)

PraveenReddy Jirra
Senior DevOps Analyst
What is Continuous Integration ?
CI is a software development practice which involves
building, integrating, and testing software components
continuously on an iterative basis. It detects defects
early on, and also reduces the risk of low quality for the
overall project.
CI Best Practices:
• Use a centralized source control system to maintain all code and project
artefacts
• Build, test, and integrate early in the project life cycle
• Automate build, test, and deployment activities
• Adopt test-driven development (TDD) practices
• Adopt continuous integration and deployment
Introduction to Jenkins

●
An extremely powerful open-source automation tool
that supports continuous build & deployment cycles
in a software project.
●
Has hundreds of plugins that make automation setup
easy
●
Has support for nearly every scripting language like
ant, maven, gradle & many more
Why Jenkins?

●
Jenkins is a software that allows continuous
integration. Jenkins will be installed on a server
where the central build will take place. The following
flowchart demonstrates a very simple workflow of
how Jenkins works
Flow Chart

Along with
Jenkins, Developers check their
sometimes, one source code
might also see the
association of
Hudson. Hudson
is a
Jenkins will pick up the
very popular
changed source code
open-source Java-
and trigger a build and
based continuous
run any tests if required.
integration tool
developed by Sun
Microsystems
which was later The build output will be
acquired by available in the Jenkins
Oracle. After the dashboards. Automatic
acquisition of Sun notifications can also be
by Oracle, a sent back to the
fork was created developer.
from the Hudson
source code,
which brought
about the
●
Flow Chart
●
Jenkins Requirements:-
Java
●
Java installation:-
sudo add-apt-repository ppa:webupd8team/java -y
sudo apt-get update
sudo apt-get install oracle-java8-installer
or
apt install openjdk-8-jdk
Jenkins Installation (Ubuntu)

wget -q -O - https://pkg.jenkins.io/debian/jenkins-
ci.org.key | sudo apt-key add -
echo deb https://pkg.jenkins.io/debian-stable
binary/ | sudo tee /etc/apt/sources.list.d/jenkins.list
apt-get update
sudo apt-get install jenkins
Jenkins Installation (centos)
Java :--
sudo yum install java-1.8.0-openjdk.x86_64
Jenkins:--
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.key
yum install jenkins
sudo systemctl start jenkins.service
Thank you

Praveen

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy