Continuous Integration

Codecademy Team
Learn how keep your code ready for deployment with continuous integration.

The Problem

Daryl and his star team of developers are working on new features for their popular mobile game. Each of the developers have been working on separate branches for the last week. Now they are all confident in their code and are ready to merge in their changes. They begin the merge process and see their console fill with conflicts! Daryl sighs, he had plans for this weekend. This could have been prevented if they had used a continuous integration approach.

What is continuous integration?

Continuous integration (CI) is a practice that consists of two main components:

  • Merging source code changes on a frequent basis.
  • Building and testing the changes in an automatic process.

The combination of these components ensures new additions are built and tested often.

CI practices can be implemented on their own. However, they are often mentioned alongside continuous delivery and deployment (CD). The combination of continuous integration, delivery, and deployment is called CI/CD. More can be learned about continuous delivery and deployment here.

CI often requires changing the way we work with source control management. Let’s take a look at why CI might make us want to move away from traditional feature branch development.

Feature branch development

In the past, traditional source control management approaches used long-lived branches. These branches were merged only once a feature was completed, hence the name, feature branch development. This works well for smaller projects or for a single developer. However, issues arise with bigger projects:

  • There are long review periods for relatively larger feature branches.
  • There could be many conflicts when merging large branches into the main repository.

Remember that the goal of CI is to frequently merge, build, and test code changes on one main branch. Feature branch development cannot be the solution due to the slow cycle of merges and relatively larger branch sizes.

Let’s discuss an approach to source control management compatible with CI.

Trunk-based development

Trunk-based development is frequently merging small changes into the main branch (or trunk). Some of the benefits of trunk-based development include:

  • Discovering problems early (known as “shifting left”) instead of at the end of a large merge attempt.
  • Small changes mean fewer conflicts and simpler fixes.

Two branch development approaches are shown. In one, entirely new features are created and added to the repository. In the other, small changes are made more frequently.

CI with trunk-based development

CI combines trunk-based development and the automation of building and testing. After each small merge into main, the codebase is automatically built and tested. This process ensures that the repository always has valid code ready to be deployed.

Now that we have an understanding of CI, let’s look at a few tools which can help with automation.

Many of the CI tools use servers to watch for changes or triggers from the project repository. The tools can be configured to run automated tests and notify developers of any problems. Some of the most popular tools for CI are:

  • Jenkins: Open source and self-hosted which allows for complete control and configuration.
  • Github Actions: Embedded within the popular source control management system.
  • CircleCI: Works with many different source control management systems.

Learning at least one of these tools can be very helpful for a team hoping to incorporate CI practices. Let’s see how we can set up CI in a project!

Implementing CI

Implementing CI on an entire project has a few steps:

  1. Make sure that the project is using one main source branch.
  2. Pick one of many CI servers to control automatic builds and tests.
  3. Configure the CI server to trigger automatic builds when merges occur.
  4. Develop tests and configure the CI server to run them.
  5. Set up notifications for build or test failures.

This seems like a lot of extra work, but luckily there are plenty of tools to help with CI.


CI is very important to DevOps by ensuring that codebases stay in a deploy ready state. CI solves problems of feature branch development through less conflicts and fewer bugs. Through the use of popular CI tools, a project can be set up to follow CI practices. The benefits of CI have become popular with and adopted be companies and organizations all throughout the world!