Long gone are the days when software was developed as large monolithic entity and released every quarter or six months. Customers had to wait for months for their critical bug fixes or use a semi tested patch release in order to overcome blocking issues.
The current software delivery model is one of Continuous Integration and Continuous Delivery (CI-CD).
Organizations that are involved in delivering software applications to enterprises, essentially have operational goals that
In this article I am going to illustrate the CI-CD concept which addresses the goal of "Enable faster delivery" and the tools that are available to achieve the same.
CI-CD Pipeline
Typical DevOps life cycle processes in Application Development can be explained with the below diagram
The tools available for CD are
- Selenium for UI testing
- Jenkins for Deployment
RLCatalyst is a tool that provides a platform to implement CI-CD processes in an organization.
More about RLCatalyst and Continuous Testing in my next article.
The current software delivery model is one of Continuous Integration and Continuous Delivery (CI-CD).
Organizations that are involved in delivering software applications to enterprises, essentially have operational goals that
- Enable faster delivery of enterprise software
- Speed up Build and Test Cycles from current baseline
- Enable them to move to scalable architecture
- Helps add more capacity to handle increased demand
In this article I am going to illustrate the CI-CD concept which addresses the goal of "Enable faster delivery" and the tools that are available to achieve the same.
CI-CD Pipeline
Typical DevOps life cycle processes in Application Development can be explained with the below diagram
The total time for release = CI time + CD time
In order to reduce the cycle time for release, the CI time and CD time have to be reduced.
The CI time is reduced by reducing the gap between code check-in and build process.
The moment code changes are committed to the repository, the build should be triggered and output of the build be made available for the next phase in the pipeline.
The tools available for this phase are code repositories like Git / SVN and CI tools like Jenkins, Bamboo.
The CD time is reduced by automating the Testing and Deployment processes.
Typical testing includes - UI testing, Web Services testing, and Data Layer / Server side testing.
Testing at each of these layers has to be automated and integrated with the Continuous Deployment
tools.
The CI time is reduced by reducing the gap between code check-in and build process.
The moment code changes are committed to the repository, the build should be triggered and output of the build be made available for the next phase in the pipeline.
The tools available for this phase are code repositories like Git / SVN and CI tools like Jenkins, Bamboo.
The CD time is reduced by automating the Testing and Deployment processes.
Typical testing includes - UI testing, Web Services testing, and Data Layer / Server side testing.
Testing at each of these layers has to be automated and integrated with the Continuous Deployment
tools.
The tools available for CD are
- Selenium for UI testing
- Jenkins for Deployment
RLCatalyst is a tool that provides a platform to implement CI-CD processes in an organization.
More about RLCatalyst and Continuous Testing in my next article.
