Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Continuous Integration with Jenkins

You're reading from   Learning Continuous Integration with Jenkins A beginner's guide to implementing Continuous Integration and Continuous Delivery using Jenkins 2

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781788479356
Length 362 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Nikhil Pathania Nikhil Pathania
Author Profile Icon Nikhil Pathania
Nikhil Pathania
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Concepts of Continuous Integration 2. Installing Jenkins FREE CHAPTER 3. The New Jenkins 4. Configuring Jenkins 5. Distributed Builds 6. Installing SonarQube and Artifactory 7. Continuous Integration Using Jenkins 8. Continuous Delivery Using Jenkins 9. Continuous Deployment Using Jenkins 10. Supporting Tools and Installation Guide

Jenkins CD design


In this section, we will go through a very general CD design.

Branching strategy

In Chapter 7, Continuous Integration Using Jenkins, we followed a branching strategy for the CI that included the following:

  • The master branch
  • The integration branch
  • The feature branch

This branching strategy is a slimmer version of the GitFlow workflow branching model.

While CI can be performed on integration/development branches or feature branches, CD is carried out only on the integration and release branches.

The release branch

Some teams go with the strategy of having a release branch. A release branch is created after a successfully-tested code goes live in production (distributed to customers) from the master branch. The purpose of creating a release branch is to support bug fixes on the respective release:

Branching strategy

CD pipeline

We are now at the heart of the CD design. We will not create a new pipeline; instead, we will build on the existing CI Multibranch Pipeline in Jenkins. The new...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image