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)

Pipeline projects

So, let's continue on to Jenkins, where we are going to create our first Pipeline project. Go to New Item and pick the Pipeline project template. This will take you to the configuration screen, which looks a little different from what you are used to. For example, you are missing some options in the General section of the configuration. The Source Code Management section is missing. But most important of all, you get a brand new Pipeline section:

In this Pipeline section, you get a choice to pick your pipeline definition, Pipeline script or Pipeline script from SCM. For now, we are going to leave it on the Pipeline script, but later, we will see that the other option is actually way more practical. Below the definition field is a large Script field where your pipeline goes. Remember that this script will run inside the Jenkins environment, so you get various...