Almost everybody does Continuous Integration today. But the question is : How effective is your Continuous Integration? In this short article, let’s explore five important questions we need to ask about Continuous Integration (CI).

Article Series

This is the last article in a series of eight articles on Code Quality

Questions To Ask About Continuous Integration

Let’s look at them one by one:

Frequency Of Commits

How frequently is code being committed to the version control system?

It is awesome to have great CI infrastructure in place with frequent builds, wonderful unit tests and integration tests. However, if code is not committed frequently enough to the repository, all this infrastructure is sitting idle.

Whenever you think your code is in a good working state, commit it to get immediate feedback. Do this five, ten, or a hundred times a day!

Frequency Of Builds

How often are your CI builds running?

Are they running every time a commit is done, every minute, every hour, or once a day? With CI, it is important to get immediate feedback. If you are running your builds less frequently, you might be enjoying all the possible benefits of CI.

Ideally, CI should run for every commit.

What’s in the Build?

What are the various steps that are run in your CI build?

Are all of these are run in CI?

  • Code compilation
  • Unit tests
  • Integration tests
  • User acceptance tests
  • Deployment

It is desirable to have as many steps as possible as part of the CI build.

Build Performance

How fast is your CI build?

Any CI build should not take more than 10-15 minutes of time, as a benchmark. Of course, the steps involved in the build affects build performance.

As the number of steps in the build increase, the longer it takes. You need to find the right balance between the two, such as testing everything versus testing quickly.

One strategy would be to have two kinds of CI builds - one smaller frequent build, and one larger slower build that only runs from time to time.

Handling Broken Builds

This is one of the more fun events for the team. Having the member who breaks the build, buy lunch for the entire team is incentive enough for careful programming and commits! Not the least, it helps foster team building and team spirit.

Do check out our video on this:

image info


In this article, we explored the five important questions that a team using a CI infrastructure, to ask about its development process.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?