Hence, we can say it is the process of automating your code’s compile, static code analysis, documentation generation, etc for every single check in of code. The goal is to develop a robust build pipeline so that anything that breaks the pipeline is identified as fast as possible, because every single checked in change automatically leads to a complete run of the entire building pipeline. After having a successful CI for build, one can then make ‘build pipelines’ generating docs after a successful build, generating quality reports and maybe automatically deploying to/setting up test/production if one’s project have reach the expected quality and all unit, integration, smoke and qa tests pass. Ultimately, with its help we can  build our project and execute tests in a clean isolated environment each time one commit on CVS, with the help of a continuous build tool.

Share

The post Continuous Integration appeared first on Blog.