Connect a Polaris project to a repository in your SCM

Set up an SCM integration to connect a project in Polaris to a repository in Azure DevOps, Bitbucket, GitHub, or GitLab.

Overview

SCM integrations make it easy to test repositories in your organization with minimal configuration.

Important: When you test a project connected to a repository, via an SCM integration, SAST and SCA tests run in buildless mode. If source files in the repository are written in a compiled language, you can achieve more accurate results using the Bridge CLI (or associated plug-ins). See Continuous integration for Polaris for more information.

One project, one repository

Connecting multiple repositories to a single Polaris project is not supported. Within an application, you cannot connect more than one project to the same repository.

Branches

The default branch in your SCM repository becomes the default branch in your Polaris project. To test other branches in your SCM repository, you need to import them. See Add a branch to a project.

Supported SCMs

You can connect Polaris projects to repositories in the following Source Code Management (SCM) systems:

See Supported Source Code Management (SCM) systems for more information.

Test a repository's source files

Once you set up an SCM integration, you can test a repository's source files on demand, or automatically (on a daily or weekly basis). See How to test from the web UI and Test scheduling policies for more information.

Modify an SCM integration

To modify an SCM integration, follow these steps:

Note: If the access token you use for an SCM integration expires, generate a new token and follow these steps to update it.

In Polaris, open the project you wish to modify (go to Portfolio, select an application, and select a project).
Go to Settings > Integrations.
Update the integration, as required.
Enter a valid Repository Access Token and select Test your connection.
Select Save.
You cannot save changes until the connection is tested successfully.