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)

Artifacts

Now that we have a complete build and we know our code is pretty well tested and probably works as it should, we probably want to deliver our files. We are not yet ready for automated deployment, but at the very least, we want only those files we need to manually copy and paste somewhere. Go to your job configuration and add the post-build action Archive the artifacts. You can now specify the files you want to archive. At the very least, we want to archive the prod folder, but we also need to archive some node modules. The node modules could have been better; we could have copied them to the prod folder so that was all we needed to worry about, but we did not. If you want to do it, you know how. For now, we are going to specify the files one by one. So, you want to include the following files, seperated by a comma: prod/, node_modules/bootstrap/dist/css/bootstrap.min...