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)

Triggering builds remotely

In the previous chapters, we have looked at the various build triggers that are available to us. We even added the GitLab trigger with the GitLab plugin. There is one trigger we have not tried yet, which is the remote trigger. So, create a new project; I am simply naming it Remote Test, and check the Trigger builds remotely (for example, from scripts) trigger. You are now presented with an authentication token. This is your secret token that allows anyone who has it to remotely trigger the build. So, you best pick something that is not easy to guess (something like 47d6753c6f307c13edf010a2730f03a6). However, for our test, we are going to pick something that is a bit more readable and easy to type, so just put my_token in the field.

Normally, you can browse to a URL to trigger a regular build, for example, http://ciserver:8080/job/Remote%20Test/build...