A CI/CD pipeline in Cloud Manager can be triggered by some sort of event, such as a pull request from a source code repository, that is, a code change, or some sort of regular schedule to match a release cadence.
To configure your pipeline, you must:
In Cloud Manager, there are two types of Pipelines:
A Production pipelines is a purpose built pipeline that includes a series of orchestrated steps to take source code all the way into production. The steps include building, packaging, testing, validating, and deploying into all Stage environment first. Needless to say, a Production Pipeline can only be added once a production and stage environment set is created.
Refer to Configuring a Production Pipeline for more details.
A Non-Production Pipeline aims to run code-quality scans or to deploy source code into a development environment.
Refer to Configuring a Non-Production Pipeline for more details.
The following table summarizes all the pipelines in Cloud Manager along with their usage.
|Pipeline Type||Deployment or Code Quality||Source Code||When to Use||When or Why Should I use?|
|Production or Non-Production||Deployment||Front End||Fast deployment times.
Multiple front-end pipelines can be configured and run concurrently per environment.
The Front End pipeline build pushes out of the build to a storage. When an html page is served it may reference Frontend Code static files which will be served by the CDN using this storage as an origin.
|To exclusively deploy front end code containing one or more clientside UI applications. Front end code is any code that is served as a static file. It is separate from UI code served by AEM. It includes Sites Themes, Customer defined SPAs, Firefly SPAs and any other solutions.
Must be on AEM version 2021.10.5933.20211012T154732Z
Must have Sites enabled.
|Production or Non-Production||Deployment||Full Stack||When Front end pipelines have not yet been adopted.
For cases where the Front End code must be deployed at exactly the same time as the AEM Server code.
|To deploy AEM Server code (immutable content, Java code, OSGi configurations, HTTPD/dispatcher configuration, repoinit, mutable content, fonts) - containing one or more AEM server applications all at the same time.|
|Non-Production||Code Quality||Front End||To have Cloud Manager evaluate. your build success and code quality without doing a deployment.
Multiple pipelines can be configured and run.
|Run code quality scans on front end code.|
|Non-Production||Code Quality||Full Stack||To have Cloud Manager evaluate. your build success and code quality without doing a deployment.
Multiple pipelines can be configured and run.
|Run code quality scan on the full stack code.|
The following diagram illustrates Cloud Manager pipeline configurations with traditional, single front-end repository or independent front-end repository setup:
You must be on AEM version
2021.10.5933.20211012T154732Z to leverage Front End pipelines.
A user logged in as Deployment Manager role can create and run multiple front end pipelines concurrently. There is, however, a maximum limit of 300 pipelines per program (across all types).
These can be of the type Front End Code Quality or Front End Deployment pipelines.
Before you start configuring the Front End pipelines, see AEM Quick Site Creation Journey for an end to end workflow through the easy-to-use AEM Quick Site Creation tool. This documentation site will help you streamline the front-end development of your AEM Site and quickly customize your site with no AEM backend knowledge.
To learn how to configure Front End Pipeline, refer to:
With the front-end pipeline, more independence is given to the front-end developers and the development process can gain substantial velocity.
Refer to this document for how this process works along with some considerations to be aware of in order to get the full potential out of this process.
These can be of the type Full Stack - Code Quality or Full Stack - Deployment pipeline.
The following restrictions will apply:
A user must be logged in as Deployment Manager in order to configure or run pipelines.
At any time, there can only be one Full Stack pipeline per environment.
The user can configure the Full Stack pipeline for an environment to ignore or not to ignore the dispatcher configuration, If the corresponding Web Tier Config pipeline for the environment does not exist.
The Full Stack pipeline for an environment will ignore the dispatcher configuration if the corresponding Web Tier Config pipeline for the environment exists.
To learn how to configure Full Stack Pipeline, refer to: