Skip to main content

Why continuous integration is your friend?

In this post we are going learn benefits of Continuous Integration in Software Developments. Let’s understand what is continuous integration first and then we will discuss about benefits we are having.

What is Continuous Integration in software development?


As per wikipedia “Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies with a shared mainline several times a day. It was first named and proposed as part of extreme programming (XP). Its main aim is to prevent integration problems, referred to as "integration hell" in early descriptions of XP”.

In simple words, Continuous Integration means whenever any developer from the project team commit/checkin code at that time build will be created with the help of build servers and it will be automatically deployed to a specific location with the help of build server.

There are lots of open source and paid options are available for Continuous Integration like Team Foundation Server, Jenkins, TeamCity etc.

You can found a complete comparision of this tools from the following link.
http://en.wikipedia.org/wiki/Comparison_of_Continuous_Integration_Software

Benefits of Continuous Integration:


Followings are benefits of Continuous Integration and Followings are reason why continuous integration is your friend.

1) Automate everything If you don’t have CI then one of the developers needs to get latest/update code in his/her computer then create a build that will waste lot of time on the developer and ultimately we are going to loose developers productive time for this instead of writing code.

2) It will improve quality of code, Whenever any developers commits the code it will create a build and if build is not successful then it will inform all the users/developers of the using that project/build. So now developers will check quality of code regular because otherwise it will create bad impression of this developer on other stack holders of project.

3) Deployment will very easy. Earlier every time we have to deploy to a particular location manually but here stack holders of project don’t need to worry about the deploying things as it will deploy all the things properly.

4) Your code repository will be up to date every time and you don’t have to worry about it.

5) Save lots of times of developers and increase developers productivity. Take an example suppose there are five developers are working on a software project. One of the developer has committed code and another developer has taken latest version from source control at that he/she is facing problem while compile/building project he will notify the developer who has broke the things. So that developer will check and found that he forgot to commit one of the file. So again he will commit things and notify again to all. This will ultimately a productivity lose.

6) QA/Testing team does not have to wait for deployment. So if developer is committed code it will automatically create build and deploy it on specific location there will not be any dependency of development team to test new features.

That’s it. Looking at above reason I must say Continuous Integration is your best friend and ultimately a productivity booster. Stay tuned for more..

Comments

Popular posts from this blog

How to create Rest API(Web API) with ASP.NET Core 1.0

Recently Microsoft has released ASP.NET Core 1.0 RC2, I am getting lots of request from readers that about creating Web API. So I thought it will be a good idea to write a blog post about how to create Rest API(Web API) with ASP.NET Core 1.0.

So let’s get started via creating an ASP.NET Core 1.0 Web Application like following.



Once you click on ASP.NET Web Application, It will ask whether you need to create Web Application or Web API application. We are going to Web API so I am going to select Web API Application like following. Please note that in ASP.NET Core 1.0 there is no separate libraries or DLLs required for creating web APIs. This is just a project template.



Now once you click on OK It will create a Web API application with default values controller and program.cs.  As you know Program.cs is now starting point for the ASP.NET Core 1.0 application so It contains all the required configuration and startup items. Following is a code for that.
using System.IO; using Microsoft.Asp…

How to use migration with Entity Framework Core

Entity framework core is  the lightweight, extensible and cross-platform version of Entity Framework. Before some time, Microsoft has Released a new version of Entity Framework RC2. I have written a couple of blog post about Entity framework code first migration earlier for Entity framework 6.0. So there was a couple of request coming for writing a blog post about Entity Framework Core RC2 migration. So I thought it will be a good idea to give an overview how database migration works in Entity Framework Core RC2. This post will cover a basic scenario where we are going to create the database with existing ASP.NET Identity migration and then we are going to create a new model and have that migration applied in the database.

How to use Entity Framework Migrations: Let’s get started, To demonstrate entity framework core migrations, I am going to create a sample asp.net core web application like following.



Once we select asp.net core application it will appear the following dialog.



Now w…

Solution: gulp is not recognized as internal or external command- Visual Studio

Recently, After Upgrading to the newer version of Gulp, I was getting this error.  After doing lots of  finding online and in my system I was able to figure out that Modules like Gulp does not installed to the path. So when you try to run it from the command line it was showing below error.
gulp is not recognized as internal or external command How to solve : gulp is not recognized as internal or external command To solve this error we just need to create a new environment variable and set the NPM modules path there.

To create an environment variable,  Right click My Computer/ This Pc and click on properties.  It will open following windows.



Go to Advance System Settings and it will open system properties windows like below.



Click on Environment Variables it will open an environment and system variables windows like below.



Click on new System variable and put NODE_PATH in system variable name and %AppData%\npm\node_modules into the variable value like below.



Click on Ok. That’s it. N…