What Is CI/CD and Why You Should Be Using It

Spinnaker Summit
Jul 17, 2018 · 4 min read
Image for post
Image for post
Image credit: Pixabay.com

It’s common to see the buzzwords Continuous Integration (CI) and Continuous Delivery (CD) thrown around almost interchangeably, but they’re not quite the same thing.

While both are critical to smooth-running deployments, it’s important to be clear on the differences between them. Only then will you be able to fully understand the benefits and also make sure you know which one your team is actually doing (or needs to adopt).

What is Continuous Integration (CI)?

In a nutshell, CI is a development practice where developers merge their changes back into the main branch after each small task is complete (preferably on a daily basis). Once their code is in the mainline, an automated build then runs tests on the new commit to make sure it won’t break existing code.

To clarify why this is a big deal, consider what normally happens in traditional software development. A few developers will keep local changes because “it’s not ready yet”, while others create another branch so they can work on their own tasks without being troubled by other people’s code.

In both scenarios, problems are bound to happen after the final merge. It’s a bit like designing a car and giving each car part to a different person to work on independently, then waiting until the very last day to put the car together for testing. You’ll likely end up with a Picasso on wheels that’s brimming with issues.

Circling back to software, CI ultimately avoids untested code from merging into the main branch so teams aren’t left scrambling to fix a huge, bug-ridden mess right before release.

When to use CI?

To implement CI, you’ll have to pick a CI tool — known as build servers — like Jenkins, TeamCity, Travis CI, GitLab, Codeship, etc. Picking the right tool depends majorly on your requirements and techstack.

But when do you use CI in the first place? Basically, when you want to achieve any of the following:

  • Notify developers of issues in their code sooner rather than later.
  • Catch bugs before they reach production.
  • Push developers to write and test small chunks of code to minimize risk.
  • Build a release faster and easier by accelerating collaborative development.
  • Reduce testing costs thanks to a CI server that runs hundreds of tests in seconds.
  • Prevent integration problems with automated tests that ensure the new code works as expected and doesn’t break existing functionality.

What is Continuous Delivery (CD)?

CD is a methodology that ensures every software change is automatically built, tested, and ready to be safely deployed to production. It’s widely described as the “next step” after CI.

The main goal of CD is to reduce friction in the deployment process by automating the steps needed to fully test the code and leave it ready to be released at the push of a button. (Which relieves the developers from a lot of manual, repetitive work.)

Amazon zeroes in on the main difference between CI and CD by saying:

“Continuous integration is focused on automatically building and testing code, as compared to continuous delivery, which automates the entire software release process up to production.”

Pro tip: Continuous Delivery also tends to get mixed up with Continuous Deployment. The former involves a person/test/business rule that decides when the final push to production occurs, whereas the latter pushes changes automatically.

When to use CD?

Honestly, any organization that wants to release code faster, safer and more reliably should consider practicing CD. Popular CD tools include Ansible, Chef, Bamboo, Codenvy and many others. If multiple cloud deployments are in the picture, then open source Spinnaker is your best bet.

Here are a few more reasons why you should adopt a CD workflow:

  • Simplify the complexities of deployment so they’re no longer the bottleneck of each release cycle.
  • Ship code faster, easier, and with the confidence that nothing will break.
  • Shorten the feedback loop between users and developers from weeks/months to hours/days.
  • Push new features and updates to market more often to stay ahead of the competition (and keep users happy).
  • Fix bugs in a matter of hours, not days or weeks.
  • Increase developer productivity by automating tedious, repetitive tasks. (There’s an entire post with all the benefits of CD for developers here.)

Getting to know more about software delivery

Simply put: Businesses wanting to stay ahead of the curve need to adopt CI/CD. Furthermore, developers looking to grow their career need a strong foundation in both, since modern tech companies rely heavily on CD and have even built their team culture around it.

As a useful side note, if you’re in the business of developing, releasing, and managing software; you won’t want to miss the annual Spinnaker Summit.

The Spinnaker summit is a large-scale meetup in Seattle this October where the best developers, architects, delivery managers, and tech leaders will be giving keynotes, workshops, and their business cards. Register here and stay in the know by following Spinnaker on Twitter!

Follow us on Medium for more posts on CI/CD and open source software. Don’t forget to clap!

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store