Continuous Delivery

We are finally getting into the next portion of this book, Continuous Delivery and Deployment. But, before we continue, let's have a brief recap of what we have learned so far. When we start working on a new project, the first thing we need is some source control repository. In this book, we have used Git. Using Git, we can create multiple branches to keep different environments and features apart. In this chapter, we are going to see why this is so important. While we write the software, we want to create automated tests, such as unit tests, E2E tests, and database tests. The more useful tests you have, the more reliable your software becomes. Upon each Git commit, we want to automatically test our software using continuous integration software, in our case, Jenkins. When our tests and, optionally, static code analyzers such as JSLint and SonarQube pass...