Bitbucket Connector Settings Reference

Updated 1 month ago by Michael Cretzman

This topic provides settings and permissions for the Bitbucket Connector.

In this topic:

Limitations

  • Before Harness syncs with your Git repo, it will confirm that all Harness' settings are in a valid state. If a connection is not working Harness will not sync with your Git repo.

Name

The unique name for this Connector.

ID

See Entity Identifier Reference.

Description

Text string.

Tags

See Tags Reference.

URL Type

You can select Account or Repository.

You can add a connection to your entire Git account or just a repo in the account. Selecting a Git account enables you to use one Connector for all of your subordinate repos.

Later when you test this connection, you will use a repo in the account.

In either case, when you use the Connector later in Harness, you will specify which repo to use.

Connection Type

You can select HTTPS or SSH for the connection.

You will need to provide the protocol-relevant URL in Bitbucket Account URL.

If you use Two-Factor Authentication for your Git repo, you connect over HTTPS or SSH. HTTPS is requires personal access token.

For SSH, ensure that the key is not OpenSSH, but rather PEM format. To generate an SSHv2 key, use: ssh-keygen -t rsa -m PEM The rsa and -m PEM ensure the algorithm and that the key is PEM. Next, follow the prompts to create the PEM key. For more information, see the ssh-keygen man page.

Bitbucket Account URL

The URL for your Git repo. Make sure that it matches the Connection Type option you selected.

If you selected Repository in URL Type, enter the full URL for the repo.

If you selected Account in URL Type, enter the URL without the repo name. When you use this Connector in a Harness setting you will be prompted to provide a repo name.

Authentication

Readonly Bitbucket repos also require username and password/token.

You can use a password/token for HTTPS credentials.

If you selected SSH as the connection protocol, you must add the SSH Key for use with the connection. 

If you log into Bitbucket using a Google account, you can create an application password in Bitbucket to use with Harness. For steps on this, see App passwords from Atlassian.

Username

The username for the account.

Password/Personal Access Token

A Harness Encrypted Text secret for the credentials of your Bitbucket user account.

If you have set up Two-Factor Authentication in your Bitbucket account, then you need to generate a personal access token in your repo and enter that token in the Password/Token field.

SSH Key

If you selected SSH as the connection protocol, you must add the SSH Key for use with the connection as a Harness Encrypted Text secret.

Enable API access

This option is required for using Git-based triggers, Webhook management, and updating Git statuses. If you are using Harness Git Experience, you will need to use this setting.

API Authentication

A Harness Encrypted Text secret for the credentials of your Bitbucket user account.


Please Provide Feedback