FP Complete

Continuous Integration and Continuous Deployment, often abbreviated as CI/CD, are two closely related techniques that are central to a good DevOps story. They both involve the automation of some activity with your code based on some predefined triggers. Due to this similarity, they are often implemented with the same set of tooling. CI/CD is usually the first step on the road to adopting DevOps. Let’s step through what they are and how to approach them.

Continuous Integration

Continuous Integration, or CI, is about automatically building, testing, and optionally creating a runnable archive of your project. It typically runs on every commit pushed to your version control system (VCS), such as Git. Sometimes more expensive integration tests only run on stable branches like master or staging, depending on your VCS workflows. There are some semi-obvious benefits to adopting CI:

Subscribe to our blog via email

Email subscriptions come from our Atom feed and are handled by Blogtrottr. You will only receive notifications of blog posts, and can unsubscribe any time.