CI/CD

You must be confused between DevOps and CI/ CD.

‘CI stands for Continuous Integration and CD stands for Continuous Delivery/ Deployment.’

We know, in development and implement life cycle there are multiple steps involved e.g., development of code, packaging it, testing it, and then deploying in production.

The challenge in traditional approach is, once development is completed rest of the steps in above cycle were very time consuming as there are a lot of manual processes involve plus dependencies on many departments for review, approval, and deployment manually. Due to manual processes, there was always risk of human errors. Many a times, we have seen one deployment can affect other’s code as well. For example, there are 5 deployments conducted at the same time, 4 deployments went smooth but 5th one impact last 4 as well. We won’t go into details but trust me, I have personally seen the above incidents many times. OK OK OK, yes once me deployment screwed other deployments as well lolz 😊. The point is whenever there is human involvement, errors are inevitable.

To cater to the above challenge, CI/ CD approach came on to surface where using tools and technologies, whole above-mentioned cycle is automated.

Once development is done, code is pushed to CI process which builds and test the code before passing to CD process which then builds, configure, package, and deploys in such a manner that it fulfills all production ready standards.

With the help of CI/ CD, where the whole cycle used to take days and sometime weeks, now the cycle has been reduced to minutes for small deployments.

CI/ CD directly supports agile development so mini code deployments can take place as well.

‘The future is CI/ CD for any or every kind of release management.’