Release notes for Cloud Manager 2021.11.0 release-notes-for

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

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.

The Pipeline card, with zero pipelines, now provides you 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 expand in scope along with the details provided.

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

The Edit Pipeline API now supports setting the Dispatcher invalidation and flush paths.

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.

The Manage button in the Environments page is no longer visible in the UI.

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 maximum number of repositories was reached, did not specify the reason for the error.

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