Add external repositories in Cloud Manager external-repositories

Learn how to add an external repository into Cloud Manager. Cloud Manager supports integration with GitHub, GitLab, and Bitbucket repositories.

NOTE
This feature is only available to the early adopter program.

Configure an external repository

Configuration of an external repository in Cloud Manager consists of three steps:

  1. Add an external repository to a selected program.
  2. Provide an access token to the external repository.
  3. Validate ownership of the external repository.

Add an external repository add-ext-repo

  1. Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.

  2. On the **My Programs console, select the program to which you want to link an external repository.

  3. In the side menu, under Services, select Folder icon Repositories.

    The Repositories page

  4. Near the upper-right corner of the Repositories page, click Add Repository.

  5. In the Add Repository dialog box, select Private Repository to link an external Git repository to your program.

    Add own repository

  6. In each respective field, provide the following details about your repository:

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
    Field Description
    Repository Name Required. An expressive name for your new repository.
    Repository URL Required. The URL of the repository.

    If you are using a GitHub-hosted repository, the path must end in .git.
    For example, https://github.com/org-name/repo-name.git (URL path is for illustration purposes only).

    If you are using an external repository, it must use the following URL path format:
    https://git-vendor-name.com/org-name/repo-name.git
    or
    https://self-hosted-domain/org-name/repo-name.git
    And match your Git vendor.
    Select Repository Type Required. Select the repository type that you are using: GitHub, GitLab, or BitBucket. If the repository URL path above includes the Git vendor name, such as GitLab or Bitbucket, the repository type is already pre-selected for you.
    Description Optional. A detailed description of the repository.
  7. Select Save to add the repository.

  8. In the Private Repository Ownership Validation dialog box, provide an access token to validate ownership of the external repository so you can access it.

    Selecting an existing access token for a repository
    Selecting an existing access token for a BitBucket repository.

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
    Token type Description
    Use existing Access Token If you have already provided a repository access token for your organization and have access to multiple repositories, you can select an existing token. Use the Token Name drop-down list to choose the token you want to apply to the repository. Otherwise, add a new access token.
    Add new Access Token Repository type: GitHub
    • In the Token Name text field, type a name for the access token you are creating.
    • Create a personal access token by following the instructions in the GitHub documentation.
    • Permissions required:
      • Read access to metadata.
      • Read and write access to code and pull requests.
    • In the Access Token field, paste the token you just created.
    Repository type: GitLab
    • In the Token Name text field, type a name for the access token you are creating.
    • Create a personal access token by following the instruction in the GitLab documentation.
    • Permissions required:
      • api
      • read_api
      • read_repository
      • write_repository
    • In the Access Token field, paste the token you just created.
    Repository type: Bitbucket
    • In the Token Name text field, type a name for the access token you are creating.
    • Create a repository access token using the Bitbucket documentation.
    • Permissions required:
      • Read and write access to code and pull requests.
    note note
    NOTE
    The feature Add new Access Token is currently in the Early Adopters phase. Additional functionalities are being planned. As a result, the required permissions for access tokens may change. Additionally, the user interface for managing tokens may be updated, potentially including features like token expiration dates. And, automated checks to ensure that tokens linked to repositories remain valid.
  9. Click Validate.

After validation, the external repository is ready to use and link to a pipeline.

  1. Add or edit a pipeline:

    Pipeline's source code repository and Git branch
    Add Non-Production Pipeline dialog box with selected repository and Git branch,

  2. When adding or editing a pipeline, to specify the Source Code location for your new or existing pipeline, choose the external repository you want to use from the Repository drop-down list.

  3. In the Git Branch drop-down list, select the branch as the source for the pipeline.

  4. Click Save.

TIP
For details about managing repositories in Cloud Manager, see Cloud Manager Repositories.

Limitations

  • External repositories cannot be linked to Configuration pipelines.
  • Pipelines using external repositories (excluding GitHub-hosted repositories) and the Deployment Trigger option On Git Changes, triggers are not automatically started. They must be manually started.
recommendation-more-help
c6cdc82b-cee9-48e0-a6ee-48149d5e72c3