Connect Polaris to Multiple SCM Repositories

Overview

Bulk onboarding into Polaris features include:

Using your Source Code Management (SCM) repository to create new application(s) and project(s), or add multiple repositories to existing applications in Polaris.
- Automatic mapping: Polaris creates an application for each organization/group that can be accessed using the access token, and it creates a project for each repository.
- Customizable mapping: Manually select the organization/group 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).
Assign policies and roles while onboarding.
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.
Access to:
- Synchronizing your SCM provider with Polaris
- Event-Based Test Automation
- PR comments

General Prerequisites

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

A concurrent subscription (in Polaris) 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 access token provided will be subject to rate-limits on SCM. If the rate limit is reached, the system does not automatically retry the operation.
You cannot import repositories that do not belong to a supported SCM or SCM organization.
Only one active bulk onboarding job is allowed per tenant.
Access token must be created by an Organization Owner in the SCM organization and have specific requirements/scopes:

Support

Within the Polaris UI, SCM repository bulk integration is supported for:

Update your SCM connections within an application

Update or add new access token to your SCM provider. If your token has expired or you need to update the scope in order to setup synchronization or event-based testing, follow these steps.

On the Portfolio page, select an application by clicking on its name.
Click Settings > Integrations.
Click Edit icon next to Connected SCM.
Enter the updated access token created in the SCM 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 you have authorized use of access token outside SSO (if applicable).
If connection is successful, click Save.