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)

Database

Databases are really difficult to update automatically. As I have mentioned somewhere earlier in this book, you will often face customers or database administrators who flat out forbid you to do any updates on a database, let alone do so automatically. It is not uncommon that developers deliver their scripts to a person, typically the DBA, who then manually checks them and runs them on the database. For good reason, the database stores what a business is all about or what it needs to run properly--data. Losing or damaging it can put a company out of business (but, of course, you have backups).

Less severe, but potentially damaging to the business, are scripts that lock tables, update live data, or change business rules. You can imagine that some scripts, such as updating a 1,000 GB table, can potentially lock an entire system. Such updates should happen outside of business...