Cloud Manager configuration pipeline fails when the external Git repository setup is incorrect
Cloud Manager configuration pipelines can fail during Build & Unit Testing when Cloud Manager cannot download files from an external Git repository. This usually happens after repository URL changes, branch changes, BYOG validation issues, provider-side access changes, or stale pipeline metadata. The failure often appears as a repository endpoint or not found error even when the repository worked earlier. Verify the repository configuration, confirm ownership validation and branch setup, then retry or recreate the pipeline if the connection is still correct.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Cloud Manager configuration pipelines
- External Git repositories linked through BYOG
Issue/Symptoms
- The
Build & Unit Testingstep fails while downloading configuration files from the external repository. - The build log shows Error while processing the download and upload to shareName. Cause: The provided repository URL does not point to a valid endpoint. The external service responded with a ‘not found’ error.
- The pipeline previously worked but starts failing after a repository URL change or branch change.
- Other pipelines using the same repository succeed, but one specific configuration pipeline fails.
- The failure is intermittent for the same repository and branch combination.
Cause
The configuration pipeline build step uses Cloud Manager repository services to retrieve files from the configured external Git repository. If Cloud Manager cannot retrieve the expected branch or path, it returns a repository endpoint or not found error. This can happen because of an incorrect repository URL, an incorrect branch, missing BYOG validation files, outdated or missing repository authentication, provider-side access restrictions, stale repository references in code, transient Git provider failures, or stale pipeline metadata.
Resolution resolution
To resolve Cloud Manager configuration pipeline failures when using an external Git repository, follow these steps:
- Open the failing pipeline in Cloud Manager and confirm that the build log shows the repository download failure.
- Review the configured repository URL and branch in the pipeline settings and correct either value if it does not match the external Git provider exactly.
- If the repository uses BYOG with GitHub, verify that
.well-known/adobe/cloud-manager-challengeexists in the same branch configured for the pipeline. - Open Cloud Manager
>Repositories, select the linked repository, and refresh or update the repository connection if that option is available. - Confirm with the Git provider that the repository is reachable and that no provider-side permission or network restriction blocks Cloud Manager access.
- Rerun the pipeline once or twice to rule out a transient external Git provider failure.
- If the failure continues and the repository configuration is correct, delete the failing configuration pipeline and recreate it with the same repository and branch.
- If the pipeline still fails after recreation, review project files such as
pom.xmlor other module configuration files for outdated repository references and update them if needed. - If the repository URL, branch, validation file, and provider access are all correct and the pipeline still returns the same repository error, contact Adobe Support.