CloudShell Colony in your CI/CD Pipeline

When a developer commits code to the source control repository, a new build is triggered and a new artifact is created. To update the production with the new code, a new release is created with the latest artifacts. The artifact then goes through the pipeline, while being tested on different environments, all the way to production. While testing, CloudShell Colony provides on-demand sandbox environments integrating with test tools and storage providers to pull the artifacts and push to Production using blue/green deployment strategy.

CloudShell Colony comes with out-of-the-box plugins for Azure DevOps, Bamboo, Jenkins, TeamCity and other cloud providers. Let's see an example of the pipeline steps used in Azure DevOps:

The pipeline starts a new sandbox using CloudShell Colony, runs the required tests and then ends the sandbox when done. Once environments are no longer needed, CloudShell Colony terminates them. Cloud infrastructure is not kept up if it's not in use.