Learn about CI/CD pipelines and how they handle deployments to staging and production environments in Cloud Manager.
Cloud Manager includes a continuous integration/continuous delivery (CI/CD) framework, which allows implementation teams to quickly test and deliver new or updated code. For example, implementation teams can set up, configure, and start an automated CI/CD pipeline that leverages Adobe coding best practices to perform a thorough code scan and ensure the highest code quality.
The CI/CD pipeline also automates unit and performance testing processes to increase deployment efficiency and proactively identify critical issues that are expensive to fix after deployment. Implementation teams can access a comprehensive code performance report to gain visibility into potential impact on KPIs and critical security validations if the code gets deployed to production.
This diagram illustrates what happens once a release is triggered in Cloud Manager using a pipeline.
|1. Start a release||A deployment manager triggers a release either manually, with a git commit, or based on a recurring schedule.|
|2. Create release tag||Cloud Manager creates a git tag to mark the release using an automatically generated version number, e.g.
|3. Built as release with auto-generated version||Cloud Manager builds the application with the newly-assigned version number.|
|4. Evaluate code quality||Cloud Manager scans the source code and provides a summary before code can be deployed to the staging environment.|
|5. Versioned artifact(s) stored||The release artifacts are stored for later usage in the deployment steps.|
|6. Automatic deployment of artifact(s) to AMS AEM staging||The release artifact is deployed to the staging environment.|
|7. Trigger automated tests||Cloud Manager runs performance and security tests on the artifact.|
|8. Production trigger deployment||After the automated tests are complete, Cloud Manager starts the deployment to production.|
|9. Cloud Manager gets artifacts(s) to deploy||Cloud Manager pulls the stored release artifacts.|
|10. Deploy artifacts(s) to production||The release artifacts are deployed to the production environment.|
The CI/CD pipeline provides quality gates, or acceptance criteria, which must be met before the code can be moved from the staging environment to the deployment environment. There are three gates in the pipeline:
For each of these gates, there are three levels of issues that can be identified:
This is an example of a code scan with issues identified.
See the document Configuring Production Pipelines for details on setting up your code, quality, and performance gates.