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)

Executing Gulp in Jenkins

Running your build should now be easy, because it is just another shell command. The only problem is that we do not have Gulp, Karma, or any other tool installed globally on our VM, so a gulp or karma start command will fail. Any command-line tool installed through Node.js will have their executables in the node_modules.bin folder (which is why we installed all those tools in our project in addition to globally on our development machine). So we can now simply run node_modules/.bin/gulp. The shell still operates from the root of our project and so will also use our local gulpfile.

Unfortunately, a lot will go wrong. Your tests will fail, the browsers will not start, and your job will never finish. You may have already guessed why. First, we do not have any browsers installed on our Ubuntu machine. We do not even have a user interface! So, of course, Jenkins...