This procedure describes how to onboard one or more Azure DevOps repositories to new or existing Polaris applications. During this process, you'll have the option of importing all repositories in your Azure DevOps instance or choosing specific repos to import.
Before you begin, review Integrate Azure DevOps with Polaris. If you're using Azure DevOps Server, that topic explains how to make sure Polaris has network access to your ADO Server instance. Create a personal access token as described in Azure Tokens for SCM Bulk Integration and/or Monitoring before proceeding.
Important:
Bulk SCM integration with Azure DevOps Cloud requires a Polaris Premium subscription.
Note: SCA Fix Pull Requests are supported for repositories hosted in Azure DevOps Cloud and Azure DevOps Server. For Azure DevOps Server integrations, Polaris creates the pull request over the Secure Tunnel that connects it to your repository. See SCA Fix Pull Requests.
Onboard Azure DevOps repositories to Polaris applications
Next steps
- Set up event-based test automation. See Event-Based Test Automation in Polaris for SCM Integrations. Note: To enable Fix Pull Requests for all onboarded applications, create a component policy (see Component policies) and assign it to the applications after onboarding. See SCA Fix Pull Requests.
- Scan on demand (see How to test from the web UI) or schedule automatic testing on a daily or weekly basis (see Test scheduling policies). Note: From the Tests screen, before beginning a test manually, make sure to test the connection.
- Change settings or add sync options. See Synchronizing Polaris with your SCM Provider.
- (Azure DevOps Server) CI/CD pipelines integrating with Azure DevOps Server via the Secure Tunnel may require
HTTPS_PROXYorHTTP_PROXYenvironment variables to route traffic correctly. See Using Bridge CLI with Polaris.