Integrate Multiple SCM Repositories

Prerequisites

Within the Polaris UI, Source Code Management (SCM) repository bulk integration is supported for:

GitHub
GitHub Enterprise Cloud

The following roles can initiate bulk onboarding:

Organization Admin
Organization Application Manager
Application Admin (limited to bulk onboarding projects and SCM connections for applications they are the admin for).

Assumptions and constraints

Only covers SaaS GitHub (hosted Git deployments are out of scope).
A concurrent subscription is required to use this feature.
Users can only import repositories from organizations they are a member of; they cannot import repositories from public orgs that they are not a member of.
Only 100 repositories per hour will be onboarded. The personal access token provided will be subject to rate-limits on GitHub. If the rate limit is reached, the system does not automatically retry the operation. See Rate limits for the REST API - GitHub Docs for more information.
You cannot import repositories that do not belong to a GitHub organization.
Only one active bulk onboarding job is allowed per tenant.

Overview

Bulk onboarding into Polaris features include:

Using your SCM repository to create new application(s) and project(s), or add multiple repositories to existing applications in Polaris. During this process the user can assign policies and roles:
- Automatic mapping: Polaris creates an application for each organization that can be accessed using the personal access token, and it creates a project for each repository in each organization. Application and project names match organization and repository names from GitHub, respectively.
- Customizable mapping: Manually select the GitHub organizations and repositories you wish to add to Polaris. Use this option to create multiple repositories to be imported to a new application(s) or existing application(s).
Ability to update the connection credentials for all the projects under an application.
Import SCM repositories as projects into an existing application and assign policies to it.

In order to use any of these features, you will need to create a personal access token in GitHub.

Creating a personal access token

When integrating SCM repositories, you will need a personal access token you create in GitHub .

Note: The personal access token will be used to complete the onboarding process and will be subject to rate limits enforced by GitHub.

Note: Use of personal access token (classic) is recommended.

Sign in to GitHub.
In the upper-right corner of any page, click your profile photo, then click Settings.
In the left sidebar, click Developer settings.
In the left sidebar, under Personal access tokens, click Tokens (classic).
Select Generate new token, then click Generate new token (classic).
Name your token.
Set the token's expiration date. To avoid issues, we recommend No expiration.
Under Select scopes, access to all the permissions under repo and read:org under admin:org are required.
Click Generate Token.
(Optional) Select the copy icon to copy the token.
To use your token to access resources owned by an organization that uses SAML single sign-on, authorize the token via Configure SSO. For more information, see Authorizing a personal access token for use with SAML single sign-on in the GitHub Enterprise Cloud documentation.

Note: For more information, see Managing your personal access tokens - GitHub Docs.

Integrate application(s) and project(s) from SCM repositories

See Prerequisites before starting.

On the Portfolio page, select + Create > New Application(s) with SCM.
Connect to your SCM:
1. Select Github Standard or Github Enterprise Cloud.
2. Enter the personal access token created in GitHub (see Creating a personal access token) under Repository Access Token.
  
  Note: The personal access token provided here will be used to complete the onboarding process and will be subject to rate limits enforced by GitHub.
3. Click Connect.
  You should receive a Connection Successful message and the Quick Start options should be visible. If your connection test is unsuccessful, check the following:
  - Your network connection is stable.
  - Check the Repository Access Token to make sure it is accurate.
  - Check that the Repository Access Token is still valid and has not expired.
  - Check that you selected the correct provider for your source repository.
  - Check that your organization allows use of personal access token (classic).
  - Check that your have authorized use of access token outside SSO (if applicable).
Select method: (Repository Mapping is different depending on the selection).
- Matching Organization Names (Automatic)
- Mapping Repositories (Custom)
Assign Policies (optional): Choose Issue Policies or Test Schedule Policies, or both. All the projects created with this import will be assigned these policies.
Application Role Assignments (optional): Select users for Application Administrator, Application Contributor, Application Member and Application Observer roles.
- The user selected will have the specified role for all the applications that are being created.
- Double check that the user being assigned has access to the SCM repositories in GitHub.
Repository Mapping: This will be different according to which method is selected.
1. Automatic Mapping: Lists the matching organizational names as applications and projects. You can view repositories to be imported by using the pulldowns (read only).
2. Custom Mapping: Select New (type application name) or Existing (select application from pulldown), then select repositories from pulldowns under Projects. If an arrow is next to a name, you can click to select repositories within it. Click Add More to map repositories to multiple applications.
Click Import Repositories.
On your Portfolio page, a progress bar with a percentage done will track your progress.

If the onboarding fails, an email notification will be sent to the user who initiated the onboarding.

Click Cancel to cancel the import. Any repository in the process of being imported at the time of cancellation will complete in the background after the cancel is accepted. Then all onboarding will be stopped immediately. For example, if you import ten repositories and cancel at 50%, five repositories would be imported and five repositories would not.

Manage your SCM connections within an application

Updates all projects in an application using the SCM provider.

On the Portfolio page, select an application by clicking on its name.
Click Settings > Integrations.
Click Update SCM Integration.
Select Github Standard or Github Enterprise Cloud.
Enter the personal access token created in GitHub (see Creating a personal access token) under Repository Access Token.
Click the Connect button.
You should receive a Connection Successful message. If your connection test is unsuccessful, check the following:
- Your network connection is stable.
- Check the Repository Access Token to make sure it is accurate.
- Check that the Repository Access Token is still valid and has not expired.
- Check that you selected the correct provider for your source repository.
- Check that your organization allows use of personal access token (classic).
- Check that your have authorized use of access token outside SSO (if applicable).
If connection is successful, click Update Authentication.

Bulk integrating projects into an application

See Prerequisites before starting.

On the Portfolio page, select an application by clicking on its name.
On the Application page, select + Create > New Project(s) with SCM.
Connect to your SCM:
1. Select Github Standard or Github Enterprise Cloud.
2. Enter the personal access token created in GitHub (see Creating a personal access token) under Repository Access Token.
  
  Note: The personal access token provided here will be used to complete the onboarding process and will be subject to rate limits enforced by GitHub.
3. Click Connect.
  You should receive a Connection Successful message. If your connection test is unsuccessful, check the following:
  - Your network connection is stable.
  - Check the Repository Access Token to make sure it is accurate.
  - Check that the Repository Access Token is still valid and has not expired.
  - Check that you selected the correct provider for your source repository.
  - Check that your organization allows use of personal access token (classic).
  - Check that your have authorized use of access token outside SSO (if applicable).
Assign Policies (optional): Choose Issue Policies or Test Schedule Policies, or both. All the projects created with this import will be assigned these policies.
Repository Mapping: Select repositories to import as new projects from pulldowns. If an arrow is next to a name, you can click to select repositories within it.
Click Import Repositories.