{"id":10334,"date":"2019-08-13T11:47:50","date_gmt":"2019-08-13T11:47:50","guid":{"rendered":"https:\/\/www.bacancytechnology.com\/blog\/?p=10334"},"modified":"2024-03-04T04:26:35","modified_gmt":"2024-03-04T04:26:35","slug":"continuous-integration-and-continuous-deployment-a-gentle-introduction-of-ci-cd","status":"publish","type":"post","link":"https:\/\/www.bacancytechnology.com\/blog\/continuous-integration-and-continuous-deployment","title":{"rendered":"Continuous Integration & Continuous Deployment: A Gentle Introduction"},"content":{"rendered":"

Hola, being a software developer, you must be familiar with the term CI\/CD, but do you know what does it mean? As defined in Wikipedia<\/a>, CI\/CD is referred to as the combined practices of continuous integration and continuous delivery and\/or continuous deployment<\/strong>.<\/p>\n

Today most of the organizations are adopting Agile and follow sprints. Sprint includes tickets and developer are required to write codes to resolve the issue of those tickets. Sometimes we need to HotFix some bugs on production which are not part of tickets for that we also need to write codes and deploy them as well. You will be surprised to know that Amazon\u2019s software engineers are deploying code every 11.7 seconds on average with almost zero downtime, on the other hand, Netflix developers are deploying code thousands of times a day<\/strong>.<\/p>\n

CI stands for Continuous Integration and CD stands for Continuous Deployment. Let\u2019s have a look in detail. <\/p>\n

\"Ci<\/p>\n

1.Continuous Integration (CI):<\/h2>\n

As word describe CI integrate code into a shared repository several times a day. With each branch push on shared repository branches, i.e., \u201cgit push\u2026. \u201c<\/strong>this will check and verify by an automated Test and build, allowing development teams to identify problems early before code is going to deploy on the production server.<\/p>\n

Let assume what if we are performing code integration regularly, by doing this, we can detect errors\/bugs more quickly, and It\u2019s too easy to find the code which causes issue\/error. <\/p>\n

CI work-flow consists of three different stages:<\/strong><\/p>\n

\"Push\"<\/p>\n

2.Continuous Deployment (CD):<\/h2>\n

Deployment plays a major role in SDLC<\/strong>; word \u201cdeployment\u201d hurts because every time we perform deployment, the stability of the application is at risk<\/strong>, that\u2019s the reason we are keeping distance between deployments<\/strong>. <\/p>\n

Generally the issue we face on the above case is if we deploy 10 changes on production and out of 10, 9 is working fine and 1 is having some minor bug, so in this case, we need to rollback all the 10 changes, and after fixing it, we are required to deploy again<\/strong>. Even if the changes are made by a dev team of 50 members then troubleshooting for bug code is also a headache. <\/p>\n

As a solution of the above approach is Continuous Delivery, the CD is having the ability to get all types of changes such as new features, configuration changes and fix bugs into production, without affecting application stability and live users<\/strong> operations. That’s cool, isn’t it! CD ensures that your code is always production-ready!<\/p>\n

\"Continuous<\/p>\n

CI\/CD Tools<\/h2>\n