Frequently Asked Questions

How can I integreate with Bitbucket repositories?

The integration process with Bitbucket varies slightly depending on whether you are working with public or private repositories. Here's a breakdown of the key differences:

Public Repositories

• Accessibility: Public repositories are open to the public, meaning that anyone can view the repository content and its history.

• Integration Setup: For public repositories, the setup process for integrating with Ketryx is generally straightforward. You do not need to use a access tokens for basic integration tasks, such as SOUP dependency analysis.

• Data Retrieval: Accessing publicly available data from Bitbucket, like pull requests or code changes still requires a Repository Access Token to access Bitbucket's API.

Private Repositories

• Accessibility: Private repositories restrict access to authorized individuals or collaborators. Only those with permission can view and interact with the repository.

• Integration Setup: When integrating with private repositories, you typically require an access token. This token ensures secure and authorized communication between Bitbucket and Ketryx for tasks like SOUP dependency analysis and Code Change Reviews.

Ketryx supports SOUP dependency analysis using an App Password for private repositories. However, we recommend using a Repository Access Token for this purpose, as this type of token can be restricted to a single repository, while an App Password has access to all repositories in the account. Additionally, only by using the Repository Access Token can you access Code Change Reviews.

It's important to consider your repository's visibility when setting up the integration, as public and private repositories have distinct access requirements. The integration guide provides specific instructions based on the type of repository you are working with, ensuring a seamless and secure integration experience.