Continuous Delivery with Jenkins

Jadson Santos
Software Engineer
CONTINUOUS
DELIVERY

Continuous Integration
• Continuous Integration is a software development practice where
members of a team integrate their work frequently, usually each person
integrates at least daily - leading to multiple integrations per day. Each
integration is verified by an automated build (including test) to detect
integration errors as quickly as possible. Many teams find that this
approach leads to significantly reduced integration problems and allows
a team to develop cohesive software more rapidly. This article is a quick
overview of Continuous Integration summarizing the technique and its
current usage.
27/11/2020 Continuous Delivery 2

Continuous Delivery and Deployment
• Continuous Delivery is a software development discipline where you
build software in such a way that the software can be released to
production at any time.
• Continuous Delivery is sometimes confused with Continuous
Deployment. Continuous Deployment means that every change goes
through the pipeline and automatically gets put into production, resulting
in many production deployments every day. Continuous Delivery just
means that you are able to do frequent deployments but may choose
not to do it, usually due to businesses preferring a slower rate of
deployment. In order to do Continuous Deployment you must be doing
Continuous Delivery.

Jenkins
Continuous Integration Server

Jenkins Introduction
• Jenkins an open source automation server which enables
developers around the world to reliably build, test, and
deploy their software.
• Jenkins works with the Job concept.
• A job is an execution that is created when an event is triggered. Be
it a commit, a period of time or even manually by the developer.
root
12345678

• Simple Job

• Configuring the Repository
• As example, let’s use a Github repository
REPOSITORY: All source files — executable code, configuration, host
environment, and data — are committed to a version control repositor (P. M.
Duvall DZone refcard #145).

• Credentials
• We created a pair of RSA keys, put the public on github and the
private on Jenkins

• Scheduling
• Every 1 hour, when there is a change in the repository (a new
commit)
CONTINUOUS INTEGRATION: Building and testing software with every change
committed to a project’s version control repositor (P. M. Duvall DZone refcard
#145).

• Build Step
INDEPENDENT BUILD: Write build scripts that are decoupled from IDEs.
These build scripts are executed by a CI system so that software is built at every
change (P. M. Duvall DZone refcard #145).
BUILD AND DEPLOYMENT SCRIPTING : Centralize all dependent libraries to
reduce bloat, class path problems, and repetition of the same dependent libraries
and transitive dependencies from project to project. (P. M. Duvall DZone refcard
#145).

• Pos-Build Actions
AUTOMATE TESTS: Automate the verification and validation of software to
include unit, component, capacity, functional, and deployment tests (P. M. Duvall
DZone refcard #145).

• Pos-Build Actions
CONTINUOUS FEEDBACK: Send automated feedback from CI system to all
cross-functional team members (P. M. Duvall DZone refcard #145).

• Build Log

• Build Configuration

• Build DashBoard
VISIBLE DASHBOARDS : Provide large visible displays that aggregate information
from your delivery system to provide high quality feedback to the Cross-Functional
Team in real time. (P. M. Duvall DZone refcard #145).

• Jenkins Configuration

• Manage Plugins

• System Configuration

• Global Tools Configuration

• Jenkins Configuration (Making the dashboard public)
• Configure Global Security
• Choose "Role-Based Strategy" in the "Authorization" section

• Manage and Assign Roles -> Manage Roles
• Create a new “public” role and give permission just to read: Overall,
Jobs and View.

• Manage and Assign Roles -> Assign Roles
• Assing “public” role to “Anonymous” user

• Now “Anonymous” users (without login) can view the dashboard

Pipeline
DEPLOYMENT PIPELINE: A deployment pipeline is an automated implementation
of your application’s build, test, deploy, and release process. (P. M. Duvall DZone
refcard #145).

Continuous Delivery Pipeline
• Pipeline is a concept to avoid waste in the software
development process and is used to provide quick
feedback to the team during the deployment process.

• How does it works?
• The software deployment is divided into different
stages, where the tasks (jobs) are performed in each
of these stages. At the same stage, tasks can be
performed in parallel, to assist in the feedback loop.
When all tasks in one stage are approved, tasks in
the next stages can begin.

• 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.
• We need to have 3 simple jobs previously created. Each
job will be 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

These pipelines only show the execution of existing Jobs in
the form of a pipeline.
That is, they organize the visualization of Jobs in sequence.
But it's still just Jobs running in sequence

Blue Ocean

Blue Ocean Introduction
• Blue Ocean rethinks the user experience of Jenkins.
Designed from the ground up for Jenkins Pipeline, but still
compatible with freestyle jobs, Blue Ocean reduces clutter
and increases clarity for every member of the team.
• Sophisticated visualizations
• Pipeline editor
• Personalization

• Install Blue Ocean

• Creating a Pipeline

• You can choose Git and enter with user and password

• Or choose Github and use your “Personal access tokens”

• Than choose the repository

• It will created a Jenkinsfile file
• This file will hold all configuration of your pipeline
REPOSITORY: All source files — executable code, configuration, host environment,
and data — are committed to a version control repository. (P. M. Duvall DZone
refcard #145).

• Infrastructure as code, ou IaC

• It is na automating process the management and provisioning of
the IT infrastructure using configuration files, rather than physical
hardware configurations or interactive configuration tools.
• This automation eliminates the need for developers to manually
provision and manage servers, operating systems, databases, and
other infrastructure elements

• Benefits.
• Uniform Configuration for All Environments
• Protection against churn
• Faster and more efficient development
• Faster time to market
• Lower costs

• With Blue Ocean plugin you can create visually the steps of your
pipeline
• Just click in the “plus” icon.

• When you click in “plus” icon you can choose several steps types

• A pipeline can be configurated in several ways
• For example we can execute a the existing job, like our “Simple
JOB” that already make the entire build of our project (clean, build
and test)

• Let’s create 3 sequential steps: clean, build and test.

• How we are using Gradle as a build tool.
• Each step of our pipeline, need just run a gradle script task.
• PS.: We need to have the gradle installed on the integration server to
Jenkins be able to execute it.

• After execution the Blue Ocean shows to show to us all steps of
execution.

• We can see the log of execution

• If some steps failed, we can see what went wrong

• The Blue Ocean Plugin committed the Jenkinksfile into our project

Blue Ocean Improve our pipeline

• Continuous Code Quality
PARALLEL TESTS: Run multiple tests in parallel across hardware instances to
decrease the time in running tests. (P. M. Duvall DZone refcard #145).
FAST BUILDS: The commit build provides feedback on common build problems as
quickly as possible — usually in under 10 minutes. (P. M. Duvall DZone refcard
#145).

• Standard sonarqube execution is very simple
• Download the community version, and run the bin/sonar.sh start
command

• The sonarqube will run at the address: http://localhost:9000
• Default User: admin
• Default Password: admin

• Add sonarqube plugin at gradle script
• And run sonarqube task

• The result will be published automatically on sonarqube

• We can see the report on sonarqube

• Add a parallel step to run sonarqube gradle task

• Allow Authentication in Sonarqube
• Administration > Configuration > General Settings > Security, and set
the force user authentication property to true

• Sonarqube tokens
• Administration > Security > Users. Once established, a token is the
only credential needed to run an analysis. Pass it as the value to the
sonar.login property

• Sonarqube tokens
• Administration > Security > Users. Once established, a token is the
only credential needed to run an analysis. Pass it as the value to the
sonar.login property
System.getProperties('my.property') = -D my.property=value

• Coverage on Sonarqube

• Continuous Delivery vs Continuous Deployment

• DataBase Migration
• Flyway: Version control for your database. Robust schema
evolution across all your environments. With ease, pleasure and
plain SQL.
SCRIPTED DATABASE: Script all database actions as part of the build process. (P.
M. Duvall DZone refcard #145).
DATABASE UPGRADE: Use scripts to apply incremental changes in each target
environment to a database schema and data. (P. M. Duvall DZone refcard #145).

• As we are using Gradle as build tool, configure the flyway Gradle
plugin

• Configure inside resources/db/migration the migrations scripts

• Example of migration script

• Configure sensitive data by Gradle parameters in step
project.property('my.property') = -P my.property=value

• As a result, a flyway_schema_history table was created and the
initial user was insert into users table.

• Deploy
BLUE-GREEN DEPLOYMENTS: Deploy software to a non-production environment
(call it blue) while production continues to run. Once it’s deployed and “warmed up,”
switch production (green) to non-production and blue to green simultaneously. (P.
M. Duvall DZone refcard #145).
PRODUCTION-LIKE ENVIRONMENTS: Target environments are as similar to
production as possible. (P. M. Duvall DZone refcard #145).

• Deploying using SSH

We can execute command
to restart the application

• Deploying to Heroku
• Heroku is a PaaS (Platform as a Service) that allows you to host up
to 5 applications for free

• Create a Heroku Application

• Install the Heroku Command Line Interface (CLI)

• Log in

• Add a Heroku rsa key.

• Add Heroku gradle plugin

• Configuring the last pipeline step

• Deploying to heroku

• Deploying to heroku
https://jadson-pipe-line-demo /calculator/sum?a=10&b=10.herokuapp.com
Your app name Service Parameters

• Complete CI/CD Pipeline

• Final Jenkins File

References
• Fowler, M., Continuous Integration
https://martinfowler.com/articles/continuousIntegration.html,
Published at May 2006. Last access at Aug. 2020.
• P. M. Duvall. Continuous delivery: Patterns and
antipatterns in the software life cycle -
https://dzone.com/refcardz/continuous-delivery-patterns.
DZone refcard #145, 2011.
• Dashboard View Plugin
• https://plugins.jenkins.io/dashboard-view/. Last access at Aug.
2020
• Jenkinks User Documentation Home. Blue Ocean
https://www.jenkins.io/doc/book/blueocean/. Last access at
Aug. 2020

References
• Gradle build. https://gradle.org/releases/. Last access at
Aug. 2020.
• Build pipelines with Jenkins 2 by example.
https://bmuschko.com/blog/jenkins-build-pipeline/.
Published 30, 2017. Last access at Aug. 2020.
• Song, Matthew. Building a CI pipeline with Blue Ocean.
https://medium.com/ecs-digital/building-a-ci-pipeline-with-
blue-ocean-6bb9b02788eb. Jan, 2019. Last access at
Aug. 2020.

References
• Jenkins User Documentation Home. Using a Jenkinsfile.
https://www.jenkins.io/doc/book/pipeline/jenkinsfile/. Last
access at Aug. 2020.
• Lloyd, Caleb. Jenkins Screencast Part 1: Setup
Jenkins Blue Ocean with Docker.
https://boxboat.com/2017/06/20/jenkins-screencast-setup-
blue-ocean-docker/. Jun, 2017. Last access at Aug. 2020.

Continuous Delivery27/11/2020 98

Continuous Delivery with Jenkins

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Continuous Delivery with Jenkins

Similar to Continuous Delivery with Jenkins (20)

More from Jadson Santos

More from Jadson Santos (18)

Recently uploaded

Recently uploaded (20)

Continuous Delivery with Jenkins