I have got a repo of all common components which are deployed to multiple brand websites . If I have to migrate this to AEM cloud service then I will create a single brand project based on the new AEM archetype. But then I also need to embed the common components package with the brand package. The pipeline in cloud manager can be setup to deploy the brand package(and embedded packages). Can I create a separate pipeline in cloud manager for common repo as well so that I can make sure that all quality gates are passed for common components ? Just trying to figure out what is the best way to setup CM pipelines in this scenario.
Though in this use case where you want to do a separate build to validate the quality of common code/ components, you can create a Non-Prod "Code Quality" pipeline (not a deployment pipeline) to run unit tests and evaluate code quality. This common code can reside in a separate branch and a new code quality (non-prod) pipeline can be configured with this branch and an appropriate trigger.