Full Stack JavaScript Strategies

Chapter 27. Building a CI/CD Pipeline

Now that you’ve gone through the process of integrating the frontend and backend along with all the infrastructure and services you need, you can automate your deployments with a CI/CD (continuous integration and continuous deployment) pipeline. That way, you can ensure that all your deployments to production or other environments run the same way each time. This is a standard for just about every organization you might work at.

Having an automated CI/CD pipeline will encourage your dev team to make small and frequent releases. You’ll partner with the DevOps team to build and maintain this pipeline. Your contribution will be having a deep understanding of how the app works and how it should run. That way, you can help set environment variables and runtime versions, and you can make sure the correct commands are being executed to get the app in a deployable state.

In this chapter, I’ll cover:

• Using CircleCI to set up a CI/CD pipeline

• Selecting tools to simplify your pipelines

• Setting up different environments and their purposes

• Using GitHub as part of your process

A lot of options and tools are available to set up your pipeline, and I’ll go through some that will get you going quickly. This is another area that crosses over with DevOps quite a bit, so you don’t have to be the expert here. Work with them to understand enough to keep your team unblocked; you can decide to go deeper from there or not. Once you’ve created your own pipeline, ...