Pipeline setup in cloud manager does not show new branches
In Adobe Experience Manager as a Cloud Service (AEMaaCS), Cloud Manager does not display newly created Git branches in the CDN configuration pipeline, preventing selection during pipeline configuration. The branch field does not retain manual input, and the dropdown list does not update with new branches. To resolve the issue, update the pipeline branch using Cloud Manager API.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- The new branch is not available in the dropdown in the pipeline configuration in Cloud Manager.
- The issue affects all configuration pipelines, including the production, development, and staging environments.
- The pipeline UI does not show the updated branch, which blocks planned deployments that rely on new branch updates.
- No explicit error message is shown in the UI, and manually entering the branch name does not persist because the value is removed when the field loses focus.
Steps to Reproduce:
- Create a new branch in the GitHub repository used by Cloud Manager.
- Open the CDN configuration pipeline in Cloud Manager.
- Attempt to select the newly created branch from the dropdown list.
- Observe that the branch does not appear in the dropdown or persist when entered manually.
Root cause
A known issue in the Cloud Manager UI prevents newly created branches from synchronizing with the CDN configuration pipeline branch selection.
Resolution resolution
Use the Cloud Manager API to update the pipeline branch when the UI does not reflect newly created branches. This approach ensures deployments continue without waiting for a UI update.
To address the issue:
-
Identify the program ID and the pipeline ID for the target pipeline in Cloud Manager.
-
Send a PATCH request to update the pipeline configuration with the required branch name.
-
Use the API request format shown below and replace the placeholders with actual values:
code language-none PATCH /api/program/<program-id>/pipeline/<pipeline-id> { "branch": "<new-branch-name>" } -
Verify that the pipeline configuration reflects the updated branch after the request completes.
If your deployment process relies on frequent branch updates, continue using this API-based approach until the UI reflects new branches consistently. Monitor Adobe Experience Manager release notes or contact Adobe Support for updates on the permanent fix.
Related reading
Cloud Manager API documentation