Scribd
Upload
49 views

Ci & CD: Continuous Integration and Continuous Deployment With Jenkins

This document discusses continuous integration (CI) and continuous delivery (CD) using Jenkins. CI involves daily developer integrations that are verified by automated builds triggered every commit. It ensures source code can be built into a working product at any time. CD automates the steps to deploy code to production servers used by customers. It aims to make the release/deployment process repeatable, reliable and automated.

Uploaded by

Eduardo Aranguiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
49 views

Ci & CD: Continuous Integration and Continuous Deployment With Jenkins

This document discusses continuous integration (CI) and continuous delivery (CD) using Jenkins. CI involves daily developer integrations that are verified by automated builds triggered every commit. It ensures source code can be built into a working product at any time. CD automates the steps to deploy code to production servers used by customers. It aims to make the release/deployment process repeatable, reliable and automated.

Uploaded by

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

CI & CD

Continuous integration
and
Continuous deployment
with Jenkins
What is Continuous integration

A development methodology

Of daily developer integrations

Verified by automated builds

Every commit triggers a build


As soon as you have completed an independent
functionality
A full build on another, empty machine
Self-testing build

Directly go from source to running build


No manual copying
No click on dialog boxes
No configuration file editing

Test with
Unit tests
Functional tests (web tests)
Performance tests

Responsible persons should be notified when


anything fails

Tests web in more browsers


What is it not

Nightly builds

Developer branches

Scheduled integration points

Building via IDEs


Why use continuous integration

Automate the build

Make the build self testing

Keep the build fast

Test in a clone of the production environment

Everyone can see what's happening

Automate deployment
Continuous Delivery

Continuous delivery/Continuous deployment

Continuous, successful and repeatable


methodology to deploying code

Automated the steps of taking checked in


code and making it run on production servers,
used by customers
8 Principles of Continuous Delivery

The process for releasing/deploying software


MUST be repeatable and reliable

Automate everything

If somethings difficult or painful, do it more


often

Keep everything in source control

Done means released

Build quality in

Everybody has responsibility for the release


process

You might also like