Pipeline steps are disabled after code scanning in AEM Cloud Manager
This article explains how to troubleshoot Adobe Cloud Manager pipeline executions in which subsequent steps become disabled after the Code Scanning stage, preventing the deployment from proceeding to Stage. To fix this, review the code-quality results, download the scan report, correct the reported code issues, and rerun the pipeline.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Adobe Cloud Manager deployment pipeline
- Stage deployment
Issue/Symptoms
- After the pipeline completes the Code Scanning stage, subsequent pipeline steps are disabled.
- Stage deployment can’t proceed.
- The Cancel or Override option isn’t available in the Cloud Manager user interface.
- No specific error message is displayed, but the pipeline user interface prevents further action.
Cause
Cloud Manager enforces code-quality gates after the Code Scanning stage. Critical findings block the pipeline and don’t support overrides. Important findings pause the pipeline and support an override only when the pipeline type and configuration allow it. The code-quality report can also contain Major findings that require correction.
Resolution resolution
Follow the steps below to resolve the issue:
-
Review the code-quality results in the Cloud Manager pipeline execution after the Code Scanning stage.
-
Use Download Details to download and review the code-quality report, such as
build_issues.csv, attached to the pipeline execution. -
Address all Critical findings and the Major findings identified in the code-quality report by updating the codebase as indicated in the report.
-
Commit and push the corrected code to the repository to trigger a new pipeline execution.
-
Check whether the Overrideoption is available:
- Resolve all Critical findings before proceeding because Cloud Manager doesn’t support overrides for them.
- Use Override for Important findings only when the pipeline type and configuration allow it.
-
If the Cancel button is disabled, canceling the pipeline isn’t available from the user interface in its current execution state. Address the code issues and rerun the pipeline after the current execution completes or times out.