Here are some feature enhancments, these can be together or even just one of these implemented would solve a lot of problems
1.) Allow the selection of artifacts to deploy to production as one of the steps before deploying to production
2.) Decouple Stage and Production deployment pipeline. Ability to deploy to Prod independently of deployment to stage
3.) Ability to start at production deployment simply by selecting previously built artifacts instead of having to start every time at the beginning of the pipeline.
Use-case:
Our product can contain ~171 modules which crashes the Adobe CM pipeline running the server out of resources.
If the production publishers are overloaded the CM deployment fails to just one publisher it aborts the entire deployment.
In the above use cases if we can start from where we left off, or select the artifacts and maybe remove failing artifacts without starting over at the beginning of the pipeline that would improve efficiency. Sometimes ou CM pipeline runs for 12 hours while it builds and deploys to production
Current/Experienced Behavior:
Unable to deploy to production and lack of robust pipelines
Improved/Expected Behavior:
Ability to deploy to stage and prod in parallel. Ability to select artifacts to deploy to production without starting hte entire pipeline over again.
Environment Details (AEM version/service pack, any other specifics if applicable):
This has been reported to the engineering under the internal reference SITES-25111. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
