The key to an efficient Software Development Life Cycle (SDLC) is to integrate, build, and deploy the code without hiccups in processes.

Cloudvanti is a Cloud Service Provider that lays the foundation for you to digitalize your services and work environment. Through the implementation of Continuous Integration (CI) and Continuous Delivery (CD), you can have your Build and Deployment Code digitalized with Cloudvanti and optimize your SDLC today.

CI/CD Concept

Continuous Integration (CI) is a software development practice in which all developers merge code changes in a central repository multiple times a day. With CI, each time a code is committed into the central repository, it triggers an automated build sequence which generates binaries that are ready for deployment.

Continuous Delivery (CD) is the automating of software deployment code process. Throughout the testing right to the live environment, all of the processes are fully automated as well as logged and visible to the entire team.

Cloudvanti CI/CD

Cloudvanti uses Azure DevOps as an orchestrator for CI/CD. We have created an integrated pipeline with Azure Repos and environment for Testing and Live. This means you can take control of your Content Management System (CMS) code in Azure Repos WITHOUT the risk of LOSING your source codes.

With the integrated CI/CD pipeline, you can easily manage the building and deployment of your website. Developers only need to commit the code in the Master branch to trigger the CI/CD pipeline.


Safe - Automated Deployments

Cloudvanti provides two working environment: Staging and Production.

Staging is the pre-Live Version, or the testing environment. Here, you can identify and squash the bugs in your code before applying the changes to the Live version.

Production is the Live version of your environment, such as the website that your customer has access.


Approval Deployments

The deployment will hold in the Staging environment and need User approval before continuing the deployment into the Production environment. Once approved, the deployment process will apply the changes in Production. Should the User rejects the deployment process, this will stop it from proceeding to Production.


Safe Deployments with No Downtime

For Production Environment, Cloudvanti deployment pipelines utilize the Azure App Service Deployment slots.

The way deployment slots work is that there will be a second server for deployment. When you deploy your code, it will be deployed into this deployment slot. Here, you can do internal testings to ensure they are working as intended. When the codes are ready to deploy, you can approve in the pipeline to swap the deployment slot with the live slot, i.e the live server now has applied the changes.

For more information about deployment slots, you can refer to this link.


Versioning Release

Cloudvanti provides the versioning release that records your deployment status. It records each deployment attempt be it failed or successful. In addition to recording, you can also rollback your code to a previous version.