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)

A NodeJS and MongoDB Web App

So far, we have tested and automated all of our HTML, CSS, and JavaScript jobs. However, all of it was frontend code. In this chapter, we are going to add some backend. We will use Node.js and MongoDB, so it will still be JavaScript. However, it will still be quite an undertaking. In our current HTML code, we have copied and pasted the entire header and search bar, but when we have a backend, we can generate HTML using a template engine. Since we are using Node.js, we can reuse our shopping-cart.js file with some slight modifications. Also, we are currently minimizing all of our code using Gulp, and hence, in using a backend, we may be able to minimize our code on the fly and have it cached.

After we have hauled over our website, so it uses a proper backend, we can run our tests to see if everything still works. However, we may have to change our tests...