Continuous Integration in Software Development and Testing

Continuous Integration (CI) is the practice of keeping the code in same repository by the developers. It can be done multiple times in a day followed by automated build which gets triggered each time code is committed. While working for an IT project for a financial product company I got first hand experience on continuous integration for the first time. They were using Bamboo server for continuous integration. For one more project done for Getskills we used Jenkins server for the same purpose. The dashboard page looks something like this

In Jenkins server we make a plan for each project which keeps the record of all the builds that have been run. The volume of builds can be arranged according to numbers or number of days since oldest build. It captures the source code from both local machine or remote repository for example Bitbucket. The advantage of continuous integration is that client or test manager can keep a check on the development being made in the project. The reports can be shown graphically or in form of screenshots or in HTML format whatever is the requirement. So this is a really good practice in IT projects to implement continuous integration to maximize the resources available and keep an eye on where the project stands.
There are a number of of more tools for continuous integration which are free on internet.

Kanav Chadha

Kanav Chadha works as advisor and consultant for Getskills ltd. He has a passion for gaining knowledge about advancements in Information and Communication Technologies.