Continuous Integration, Continuous Delivery, Continuous Deployments is collaborated goal that is to make software development and release process faster and more robust. Its main focus is on integrating and deploying the software with zero turn around time.
As soon as code is checked-in by developer in the remote repository the reviewer would review the code, if code is accepted by reviewer, build would be triggered and moved to the servers automatically which reduce the manual intervention with zero turn (least time to release the code to production) around time to production hence it would impact the people by reducing the manual intervention in processes such as code integration, merging, review, running build scripts, test scripts and deployment of different severs to production.
Continuous Delivery
Continuous Delivery is process which automates the Continuous Integration and Continuous Deployment process.The main idea is to automatically prepare and track the release to production, it would be of multiple stages, and deployment to production.
In case of continuous delivery there can be chances of the manual intervention is required to deploy to production after application acceptance testing where as Continuous deployment is the next step of continuous delivery, where changes are passed through the automated tests and then it is deployed to production automatically.
Continuous Integration
(Continuous Integration) CI would lead developers to integrate their code into the shared repository. Before CI, developer used to develop features in isolation and integrate at the end of the development but with CI approach code is getting integrated with the shared repository by each developer. One can use CI tools to integrated the latest code checked-in by the each developer a team. once can used CI tools such as Jenkins, TeamCity, Bamboo, GitLab CI, Circle CI, Code Ship, Code Fresh etc.
Code is developed and checked-in by developers using code repository such as SVN, GIT, BIT Bucket, GitHub, GitLab, Sourceforge etc. Team is merging their individual code in master branch multiple times per day.
Continuous Integration
(Continuous Integration) CI would lead developers to integrate their code into the shared repository. Before CI, developer used to develop features in isolation and integrate at the end of the development but with CI approach code is getting integrated with the shared repository by each developer. One can use CI tools to integrated the latest code checked-in by the each developer a team. once can used CI tools such as Jenkins, TeamCity, Bamboo, GitLab CI, Circle CI, Code Ship, Code Fresh etc.
Code is developed and checked-in by developers using code repository such as SVN, GIT, BIT Bucket, GitHub, GitLab, Sourceforge etc. Team is merging their individual code in master branch multiple times per day.
As Shown in Figure 1 : Continuous Delivery — Continuous Integration — Continuous Deployment.
TDD — Test driven development.
BDD — Behaviour driven development
Linting — Statics code analyser to detect the issues with code such as cyclomatic complexity.
Build- Build the Source code as single application.
Push— Check-in code to repository.
Continuous Deployment
(Continuous Deployment) CD would help people to deploy the code with no time lag between code checked-in repository and passed thought the build process along with testing(TDD and DBB)as Shown in Figure 1 : Continuous Delivery — Continuous Integration — Continuous Deployment. Continuous Integration Server would be responsible for pushing the tested and deployable code to production servers.
DevOps are set of tools and practices to automate the processes to achieve Continuous Integration, Continuous Delivery, Continuous Deployments methodology.
Conclusion
Continuous Integration, Continuous Delivery, Continuous Deployments would help people to automate the build to deployment processes which will help in smooth delivery, much happier teams, no overhead of manual testings and deployments. It would enhance the productivity of the developer, and developer can focus on the functionality and features of the application.
Comments