Over a million developers have joined DZone.

Top DZone Article of 2011: The 7 Levels of Continuous Integration

DZone's Guide to

Top DZone Article of 2011: The 7 Levels of Continuous Integration

· DevOps Zone ·
Free Resource

Planning to extract out a few microservices from your monolith? Read this free guide to learn the best practice before you get started.

I’ve noticed that when other developers talk about “continuous integration” they do not always mean the same thing.

The following is an outline of the seven stages of continuous integration based solely on my own experience:

  1. No Server, no automation - no problems
  2. Have nightly build that run each day – at least we know that the project compiles
  3. Started writing “unit” tests – now running as part of the nightly build
  4. Created a build that runs on each commits – who broke the build?!
  5. Added static code analysis and style checking to the build
  6. Server Build, deploy & run the tests on several environments also used to deploy on testing (and production) environments\
  7. Everything is automated – Even Gui tests runs automatically on the latest code, you even got as far as testing the installer. Code is analyzed and results are sent by email. Nothing is done manually unless it is done only once…

These are mine stages as I experienced them in several jobs – what are yours?


Happy coding…

Learn how to measure the impact of every feature release on performance and customer experience metrics.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}