BitBucket Integration Guide

​

Why integrate Devin with BitBucket?

Integrating Devin with your BitBucket repositories allows Devin to clone repositories, create pull requests, and collaborate effectively with your team. This integration enables Devin to work seamlessly within your existing development workflow.

​

Setting up the Integration

1. In your Devin account at app.devin.ai, go to Devin’s Workspace, and click the “Advanced Setup” button.

2. Once on the Advanced Setup page, click the “Edit” -> “Set up in VSCode” button.

3. Use the terminal within VSCode to add your BitBucket Access Token and then clone your repositories.

​

Creating an Access Token

1. Log in to your BitBucket account
2. Click on your profile picture in the bottom-left corner
3. Select “Personal settings”
4. Click on “App passwords” under “Access management”
5. Click “Create app password”
6. Fill in the following details:
   • Label: A descriptive name (e.g., “Devin Integration”)
   • Permissions: Select the required permissions (see Required Permissions section)
7. Click “Create”
8. Important: Save the token immediately as you won’t be able to see it again

​

Cloning Repositories

For BitBucket Cloud:

git clone https://x-token-auth:{access_token}@bitbucket.org/user/repo.git

For BitBucket Server:

git clone https://{username}:{access_token}@yourbitbucket.org/user/repo.git

​

Required Permissions

When creating your Access Token, ensure it has the following permissions:

• Repository Read
  • Clone and pull repository content
• Repository Write
  • Push code
  • Create and manage pull requests
• Pull Request Read
  • View pull request details
• Pull Request Write
  • Create and manage pull requests

​

Access Token Features

• Limited Scope: Access Tokens are linked to a specific repository, project, or workspace
• Single Purpose: Designed for use with a single application or integration
• No 2FA Required: Access Tokens don’t require two-step verification
• Enhanced Security: Tokens are encrypted and can’t be viewed after creation
• Granular Permissions: Permissions are specified during token creation

​

Security Considerations

• Store your Access Token securely and never commit it to source control
• Use a dedicated service account for Devin’s integration if possible
• Enable branch restrictions to enforce code review requirements
• Create separate tokens for different repositories or projects
• Remember that tokens don’t expire automatically - manage them regularly

​

External Documentation

For more detailed information, refer to these official BitBucket docs:

• Access Tokens Documentation
• Repository Access Tokens
• Project Access Tokens
• Workspace Access Tokens

​

BitBucket Integration FAQs