{"id":172,"date":"2017-08-23T11:34:52","date_gmt":"2017-08-23T11:34:52","guid":{"rendered":"https:\/\/intentwise.com\/blog\/?p=172"},"modified":"2025-04-03T02:57:43","modified_gmt":"2025-04-03T10:57:43","slug":"continuous-delivery-and-deployment","status":"publish","type":"post","link":"https:\/\/www.intentwise.com\/blog\/technology\/continuous-delivery-and-deployment\/","title":{"rendered":"Continuous Integration Delivery and Deployment","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
\"CI<\/figure>\n

Often times you see a lot of companies focus on this as an afterthought. The fundamental principle with CI\/CD<\/a> would be to help any organization to innovate faster and deliver functionalities faster to your customers. Delivering something faster to your customers should be a great incentive for any organization to do CI\/CD.<\/p>\n

CI and CD areas have matured a lot over the last few years. For someone who relies on cloud providers, there are a lot of services available which will make your journey for implementation very easy.<\/p>\n

The organization maturity level is decided by where they stand with the 3 key concepts\u00a0below:<\/p>\n

\"CI<\/figure>\n

Continuous Integration<\/strong><\/p>\n

Breaking a build should be a sin for any developer\u00a0:-).<\/p>\n

Getting your developers to understand this should be engrained in your tech culture. When there are distributed teams of developers working across the globe it’s very important to make sure that you have a stable codebase that runs all the time. Test-Driven Development(TDD) is a debatable topic. However, having no automated tests is asking for disaster. There are many types of automated tests, talking about them is a topic for another day. Having your microservices repositories plugged into a CI server and run tests and make sure that it maintains a stable branch is a fundamental ask of any CI.<\/p>\n

Continuous Deployment<\/strong><\/p>\n

Many in the industry believe that getting code into production in an automated way constitutes continuous deployment. However, due to many regulatory needs for checks and balances usually, the CD is done till the staging environment and then usually a push-button deployment to production.<\/p>\n

I strongly believe that continuous deployment is a great way to streamline your development lifecycle whether it being to a staging environment or production environment.<\/p>\n

Continuous Delivery<\/strong><\/p>\n

There is a strong need to having checks and balances at each stage to make sure that whatever the developers are committing and pushing down in the pipeline is effective, defect-free and most importantly of all doesn\u2019t break any existing features. CD^ ensures that with multiple levels of unit test, integration test, performance test and acceptance tests this whole process is streamlined and in the end can be done without fear of not breaking anything that currently exists and also to make sure that the new features are delivered according to your acceptance tests.<\/p>\n

The area where I think of CD is different is that Continuous Delivery should also make sure that there is value to an end-user in what we are delivering. It can be a bug fix, new feature or performance improvement.<\/p>\n

There are many tools available that can be leveraged to enable the CI\/CD effectively. Some of them that I feel worthwhile to review is below:<\/p>\n