Missing release branches after switching to private GitHub repository in AEMaaCS
When configuring deployment pipelines in Cloud Manager for Adobe Experience Manager as a Cloud Service (AEMaaCS) using a private GitHub repository, the branch selection dropdown does not display all release branches. Feature branches appear as expected, but most release branches are hidden despite being present in the repository and returned by the API. To resolve the issue, manually enter the full release branch name.
Description description
Environment
- Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
- Scenario: Private GitHub repository with more than 30 branches
Issue/Symptoms
- After configuring a private GitHub repository in Cloud Manager, the branch selection dropdown displays only a limited set of branches.
- Most release branches do not appear in the dropdown, even though they exist in the repository and are returned by the Cloud Manager API.
- Feature branches are visible as expected, indicating that the integration is partially successful.
Root Cause
Cloud Manager’s UI limits the number of branches shown in the dropdown. Only recently updated branches appear, while older release branches are hidden. The API retrieves all branches correctly, but the UI does not display them due to rendering constraints.
Resolution resolution
Follow these steps to resolve the issue:
- Open Cloud Manager and go to the pipeline configuration screen.
- Click the branch selection dropdown to view available branches.
- If the desired release branch is not listed, type its full name manually.
- Press Enter to confirm the branch selection.
- Save or update the pipeline configuration.
- Trigger the pipeline using the updated configuration.
- Confirm that the pipeline runs using the intended release branch.
Related reading
Configure pipelines in the AEM as a Cloud Service Tutorials