{"id":4324,"date":"2019-06-17T12:22:48","date_gmt":"2019-06-17T12:22:48","guid":{"rendered":"https:\/\/www.techuz.com\/blog\/?p=4324"},"modified":"2024-04-10T05:24:47","modified_gmt":"2024-04-10T05:24:47","slug":"what-is-ci-cd-an-introduction-to-continuous-integration-continuous-deployment-and-ci-cd-pipeline","status":"publish","type":"post","link":"https:\/\/www.techuz.com\/blog\/what-is-ci-cd-an-introduction-to-continuous-integration-continuous-deployment-and-ci-cd-pipeline\/","title":{"rendered":"What is CI\/CD? An Introduction to Continuous Integration, Continuous Deployment and CI\/CD Pipeline"},"content":{"rendered":"

Software and application development industry has gone through tremendous changes in the past decade. <\/span>
\n
\n<\/span>
\n<\/span>From the good old days when software were installed on the desktop to the web-based SaaS applications. And the transition is not just seen in the way applications are used but also in the development methodologies<\/a><\/span>\u00a0\u2014 from the traditional waterfall development to Agile and the new trend of <\/span>DevOps<\/span><\/a>. <\/span><\/p>\n


\n<\/span>
\n<\/span>But all these changes and the introduction of new methods are aimed at one thing \u2014 to enhance the <\/span>development process<\/span><\/a> and provide better products to the end user. <\/span><\/p>\n


\n<\/span>
\n<\/span>CI (Continuous Integration) and CD (Continuous Delivery\/Deployment) are such methods that are gaining momentum among developers using DevOps. In this article, we\u2019ll discuss what exactly is CI\/CD and how it can help you to develop better products.<\/span><\/p>\n


\n<\/span>What is CI\/CD?<\/span><\/h2>\n

Understanding the Terms <\/span><\/h3>\n


\n<\/span>Continuous Integration (CI)<\/b> refers to committing (integrating) the code of individual developers \u2014 several times a day into a repository and run an automated test. What this does is, it helps to detect the issues and resolve them at a very early stage. <\/span><\/p>\n

Continuous Delivery (CD) <\/b>starts when the CI ends. Once the code is committed by the developers, they are uploaded on the staging server. Here, the application is checked to ensure that it’ll work well on the production server. <\/span><\/p>
<\/br>

<\/b>Continuous Deployment<\/b>\u00a0is a different concept than Continuous Delivery. CD here refers to the deployment of the built directly to the server after the code is committed and passes the test. Adopting Continuous Integration and Continuous Deployment enables producing new working software at a faster rate.<\/span><\/p>
<\/br>

Continuous Integration<\/span><\/h2>\n

Traditionally, the developers used to work on isolated features of the application, submit the code and integrate it at the end of the cycle. This lead to spending several hours on tweaking the code and resolving issues to get it working. This task was quite daunting and cost the developers more time, efforts that resulted in deadline pressures. In the development world, this issue is known by the slang\u00a0<\/span>integration hell.<\/span><\/a><\/p>
<\/br>

That\u2019s when Continuous Integration comes it. It is a practice where developers integrate their code into the main branch of the repository several times a day. The code is then validated by creating a built and running automated tests. This continuous integration of small chunks of the codes \u2014 typically several times a day results in a seamless and easy integration that saves time and effort. <\/span><\/p>\n

\"What<\/span><\/h3>
<\/br>

Benefits of Continuous Integration<\/span><\/h3>\n