This procedure describes how to onboard one or more Bitbucket repositories to a single existing Polaris application. Each Bitbucket repository you select is mapped to a new Polaris project within that application.
Before you begin, review Integrate Bitbucket with Polaris. If you're using Bitbucket Data Center, that topic explains how to make sure Polaris has network access to your Bitbucket instance.
Bulk SCM integration with Bitbucket Cloud requires a Polaris Premium subscription.
Bitbucket Data Center: Create an HTTP access token
Authentication between Bitbucket Data Center and Polaris uses an HTTP access token (personal access token) that you create in Bitbucket. Follow the steps below or the instructions in the Bitbucket Data Center documentation: HTTP access tokens > Create HTTP access tokens.
Creating an API token
Authentication between Bitbucket Cloud and Polaris is managed with an API token that you create in Bitbucket Cloud. For additional information: Create an API token.
Onboard Bitbucket repositories to an existing application
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.
- (Bitbucket Data Center) CI/CD pipelines integrating with Bitbucket Data Center via the Secure Tunnel may require
HTTPS_PROXYorHTTP_PROXYenvironment variables to route traffic correctly. See Using Bridge CLI with Polaris.