Book Image

Continuous Integration, Delivery, and Deployment

By : Sander Rossel
Book Image

Continuous Integration, Delivery, and Deployment

By: Sander Rossel

Overview of this book

The challenge faced by many teams while implementing Continuous Deployment is that it requires the use of many tools and processes that all work together. Learning and implementing all these tools (correctly) takes a lot of time and effort, leading people to wonder whether it's really worth it. This book sets up a project to show you the different steps, processes, and tools in Continuous Deployment and the actual problems they solve. We start by introducing Continuous Integration (CI), deployment, and delivery as well as providing an overview of the tools used in CI. You'll then create a web app and see how Git can be used in a CI environment. Moving on, you'll explore unit testing using Jasmine and browser testing using Karma and Selenium for your app. You'll also find out how to automate tasks using Gulp and Jenkins. Next, you'll get acquainted with database integration for different platforms, such as MongoDB and PostgreSQL. Finally, you'll set up different Jenkins jobs to integrate with Node.js and C# projects, and Jenkins pipelines to make branching easier. By the end of the book, you'll have implemented Continuous Delivery and deployment from scratch.
Table of Contents (15 chapters)

The branching model

Now that you know how to use Git, create branches, merge them, move commits, push, pull, reset, clean, stash, and more, it is time you put this into practice. Any project should have at least two permanent branches, master and development. The development branch is where programmers put their work. When something is ready for release, it goes onto master, which should then be released.

If you do at least that, you are on your way. When a bug arises in production, you can branch from master; fix the bug on that branch, a hotfix branch if you like; and then merge that branch back into master (and release it) and development, fixing the bug for future releases.

Developers should always branch from the development branch. Any new features can be developed on so-called feature branches, sometimes also called topic branches. Once the feature is done, they can be...