Jenkins Continuous Delivery

BUILDING A CONTINUOUS
DELIVERY PIPELINE USING
JENKINS
Jadson Santos
Software Engineer

Continuous Delivery
•  Continuous Delivery is a process where you build
software in such a way that it can be released to
production at any time.
•  “Can be released to production at any time” means that
ideally, with each change the software is automatically
built, tested, packaged and stay ready for a release to
production.
28/09/16 Continuous Delivery 2

Continuous Delivery
font: https://dzone.com/articles/building-a-continuous-delivery-pipeline-using-jenk

Continuous Delivery
•  If with each change the software if ready to production,
continuous delivery requires that you have a strong
process of automated testing
•  To ensure that you do not prepare something with error to
production

Test Types
Blackbox Testing: also known as Behavioral Testing, It is
a software testing method that ignores the internal
mechanism of the system and focuses on test if the output
generated is correct for a given input. It is basically used for
validating the software.
Whitebox Testing: It’s a method of testing software that
tests internal structures an application. It is also called
structural testing and glass box testing. White-box testing
create an error-free environment by examining any fragile
code. It is basically used for verifying the software

Test Categories
Unit Testing: It is the testing of an individual unit ( in OOP
usually a class). It is the easiest to be created and is
usually the most used test category.
Integration Testing: It is a type of testing in which a group
of components are combined to produce the output. Also,
the interaction between software and the outside
components (database, REST services, etc …)

Test Categories
Functional Testing: This is a verification activity; Does
the software meet the business requirements?
Acceptance Testing: This is a validation activity; Is this
what the customer really ask for? This is usually done in
cooperation with the customer or by a customer
representative.

Test Categories
System Testing: Test the system as a whole. It is the
category that performs the test closest to how the system
will run in production. When a programmer access the user
interface of the software and simulate the use of the
software by the final user, it is a System Testing, but not
automatized.

Test Categories
Stress Testing: It evaluates how the system behaves
under extreme conditions.
Beta Testing: a sampling of the intended audience tries the
product out. It has the objective of testing the receipt of the
product on the market.

Integration vs Delivery vs Deployment
font: https://dzone.com/articles/building-a-continuous-delivery-pipeline-using-jenk

•  Continuous Integration: is a software development
practice where ideally every code commit is built and
tested.
•  One of the advantages of this practice is that you do not
have to spend a lot of time integration hundreds commits
and resolving dozens of merge problems to integrate the
software.
•  Making the integration at every commit reduces the size
of the change in the source code and small changes are
easier to manager.

•  Continuous Delivery is a approach in which teams
produce software in short cycles, ensuring that the
software can be reliably and quickly released at any
time.
•  Releasing smaller changes more often tends to produce
a software with less bugs and the bugs generated can be
solved more easily.

•  In Continuous Delivery the software can be, it is ready to
be released in production, but it is not necessary
released any time.
•  Continuous Integration is necessary for Continuous
Delivery.

•  Continuous Deployment is the next step past
Continuous Delivery, where you are not just creating a
deployable package, but you are actually deploying it
in an automated process.
•  To use Continuous Deployment we have the solve the
problem that the user is using the system, and can not
be affected at every moment with a system reboot.

•  The advantage of Continuous Deployment is that the
user can receive the change at the exact moment when
it is ready without need to reboot the system. Also know
as “zero downtime”.
•  It is a dream, but not all scenarios need this complex
requirement.
•  Therefore sometimes just Continuous Delivery is
necessary

Continuous Delivery
•  Only Continuous Integration is not enough to assure the
safe release in production.
•  Unit and integrations tests only test a developer's
perspective of the solution to a problem.
•  Without running Acceptance Tests in a production-like
environment, we know nothing about whether the
application meets the customer's specifications, nor
whether it can be deployed and survive in the real world

Continuous Delivery
•  Continuous Delivery make more likely that the
application is seamlessly deployed on the production
environment, by making the application works fine
when deployed on the test server (production-like
environment) and running Automated Acceptance
Tests.
•  More about Automated Acceptance Tests:
•  https://www.thoughtworks.com/pt/insights/blog/
acceptance-test-automation
•  https://www.katalon.com

Continuous Delivery Pipeline
Steps of your pipeline
•  Compiling the Source Code
•  Run Unit Testing
•  Packaging the application and Deploying it on a web
serve

Jenkins
Jenkins is an extensible, open source continuous
integration server.
It builds and tests your software continuously and monitors
the execution and status of remote jobs, making it easier
for team members and users to regularly obtain the latest
stable code.

Jenkins Instalation
Download the jenkins.war file and copy inside de tomcat
webapp directory

Jenkins Instalation
Start tomcat and access: http://localhost:8080/jenkins

•  Usually the more common way to work with continuous
delivery is create a pipeline to easily see and manage
all stages of build process.
•  We will create a simple 3 stages pipeline where each
stages is a job on Jenkins

•  To create our pipeline sequence let’s create 3 simple
jobs:
•  Each job execute a Gradle task in the sequence:
•  1- Compile à 2- Test à 3- Package and Deploy

•  For create this jobs you will need to install the Gradle
and Git jenkins plugins because we will use an
example project of GitHub and this project use a Gradle
as build tool.

•  For this demo, the Jenkins just orchestrate the sequence
of the pipeline, who actually performs the tasks is the
Gradle build tool.
•  To know more about how compile, execute the tests,
package and deploy a project using Gradle consult:
•  https://guides.gradle.org/building-java-applications/
•  https://docs.gradle.org/current/userguide/
web_project_tutorial.html
•  https://gradle-ssh-plugin.github.io

•  Example of a JOB
•  Step 1: Clone Source Code from GitHub

•  Step 2: Invoke Gradle taks to execute the task of pipeline
stage that the job represents

•  Step 3: In Post Build Actions call the next job that will
execute the next stage of pipeline

•  Jenkins has some Pipeline Plugins
•  We will demonstrated 3 Jenkins plugins:
•  Pipeline Plugin
•  Build Pipeline Plugin
•  Blue Ocean Plugin
•  You will need to install than in the Jenkins

With Pipeline Plugin

•  Go to new job, choose the option “pipeline”

•  In the pipeline script, define the stages of your pipeline
with it specific syntax, each job is a stage of pipeline

•  Now execute the pipeline job the it will be show the
execution of each pipeline stage

With Build Pipeline Plugin

•  This plugin uses a view as pipeline, instead a job.
•  Create a new view and choose “Build Pipeline View”

•  In the “Pipeline Flow” section select the first job as a
initial job (each job was configured to call the next job of
the pipeline in the post action build section)

•  Now change to the pipeline view that was create and you
will see all stages of the pipeline and can manage it

With Blue Ocean Plugin
•  Blue Ocean is a new project that rethinks the user
experience of Jenkins.
•  It has a sophisticated visualizations of CD pipelines and
visual pipeline editor that makes automating CD
pipelines approachable by guiding the user through an
intuitive and visual process to create a pipeline.

•  Open the Blue Ocean perspective

•  Select the source code repository

•  Inform the credentials to access the source code
repository
•  It is necessary because the Blue Ocean plugin will
commit a JenkinsFile file in the repository

•  If the repository has no JenkinsFile file yet, the plugin
will open a visual editor to define the pipeline steps

•  Clicking in each step you can define actions, that in this
demo, the action will be execute a Jenkins job

•  The visual editor will generate the JenkinsFile file and
commit it in the source code repository

•  Now just run the pipeline that the 3 jobs will be executed
•  All information about the pipeline execution will be show
on Blue Ocean view.

References
https://dzone.com/articles/building-a-continuous-delivery-
pipeline-using-jenk
https://code.tutsplus.com/tutorials/introduction-to-jenkins-
an-open-source-continuous-integration-server--cms-23879
https://jenkins.io/doc/tutorials/create-a-pipeline-in-blue-
ocean/
https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+Plugin

Continuous Delivery28/09/16 47

Jenkins Continuous Delivery

More Related Content

What's hot

Similar to Jenkins Continuous Delivery

More from Jadson Santos

Recently uploaded

Jenkins Continuous Delivery