Release Notes for Cloud Manager in Adobe Experience Manager as a Cloud Service 2021.11.0 release-notes

Users can now use new Front End pipelines to deploy Front End code exclusively in an accelerated manner. See Cloud Manager Front End Pipelines to learn more.

Optimizing the code analysis process greatly reduces the Code Quality pipeline duration. This workflow eliminates the need to build an entire AEM image, streamlining the workflow. This change is rolling out progressively over the weeks following the release.

The Git Commit ID is now displayed in the pipeline execution details making it easier to track the code that was built.

Program Creation is now available through the publicly exposed API.

Environment Creation is now available through the publicly exposed API.

The x-request-id response header is now visible in the API Playground on developer.adobe.com/. This header is useful when submitting customer care issues for troubleshooting.

As a user, I see that the Pipeline card, with zero pipelines, provides me with appropriate guidance.

A new Activity Page is now available where activities such as pipeline and code executions can be viewed along with their associated details. Over time, the activities listed in this page will expand in scope along with the details provided.

The new Pipelines page now features an on-hover status popover, allowing for a Quickview of summary details. Pipeline executions can be viewed along with their associated details.

The Edit Pipeline API now supports changing the environment used in the deploy phases.

An optimization in the OakPal scanning process has been introduced for large packages.

The quality issue CSV file now contains the timestamp for each quality issue.

Certain unorthodox build configurations resulted in unnecessary files being stored in the pipeline’s Maven artifact cache, which resulted in extraneous network I/O when starting and stopping the build container.

Pipeline PATCH API fails if the deploy phase does not exist.

The ClientlibProxyResourceCheck quality rule was producing false positive issues when there were client libraries with common base paths.

The error message when the max number of repositories has been reached did not specify the reason for the error.

In rare cases, pipelines were failing due to inappropriate retry handling of certain response codes.