Continuous Integration to Gated Validation to Continuous Delivery to Continous Feedback

The Continuous Integration Philosophy

It started with the concept of continuous integration where both developer and tester with thin line in their approach of coding(more on this later) use to write code both production and test automation and use to integrate it pretty frequently. Continuous integration has helped developers integrate their code with the main product continuously and see its impact to the overall product stability. I mean gone are the days where a developer has to wait for months to know what he has broken. Thanks to quick validation…So that means continuous integration is nothing without continuous validation.. yeah…

Well let’s try to explore this further….

The Gated Validation Philosophy 

Well we talked about continuous integration and continuous validation…Let go to the next gen gated validation….

We typically write code and integrate with the whole system by promoting it to the source control…However many times(well i am talking about myself) we break the whole system post check-in…Bringing the whole system down, leaving the other developers handicapped as they can’t check-in…Hmm and then you are embarrassed as all eyes on you…

Not only this you have screwed your manager resource utilization matrix, time to deliver to market matrix and oh god what not…

Another really disappointing scenario…A new developer in a company, trying to impress his/her boss and what the heck he has done, destabilize the product…Really bad…Next time he would go to temple before promoting code to source control system…

Well the gated validation build infrastructure is here for the rescue…

What a gated validation build infrastructure essentially does is , it does all kind of validation for the piece of code that you are trying to promote with respect to the whole product. For instance when we integrate developer’s code with the whole product it would do checks like, would it compile or would all unit test pass or would all regression test pass or would it increase the code coverage or decrease the code, etc….and then the check-in to the whole system occurs…

This ensures your code would not be promoted to source control unless your code pass all validation w.r.t the whole product…

The continuous delivery Philosophy 

As mention previously if we have a gated check-in or gated code promotion system in place then we don’t have to worry about the product stability as the system would always be ready for shipment to the customer…Hmm now here your build master is like a hero, as he has reduce time to deliver to market to virtually every check-in or every build…I always say that we are in the most exciting time of software delivery era..

The continuous Feedback Philosophy 

Post delivering software virtually with every check-in or every code promotion to source control, next phase is continuous feedback where if any error appears in the delivered code then reporting is done back to the development team through services and based on the priority of the bug the develop team can fix it.. once fixed and promoted to source control and delivered to client (most importantly sometimes without client’s knowledge) the loop is closed with the fastest way…

Leave a Reply

Your email address will not be published. Required fields are marked *