Bitbucket

Partial. Bitbucket repository binding is available. Issue tracker support is coming soon; use Linear or Jira for issue management in the meantime.

The Bitbucket integration enables workflows to bind to Bitbucket repositories and access repository content. Full issue tracker support (issue CRUD, comments) is in progress.

What you can do (today)

Repository binding: link a Rensei project to a Bitbucket repository (Cloud or Server)
Git operations: agents can clone, read, and commit code
Webhook ingestion: receive repository events (push, pull request) and trigger workflows

What's coming soon

Issue tracker: create, update, search Bitbucket issues
Pull requests: full PR lifecycle management
Deployment tracking: monitor Bitbucket Deployments

Repository credential setup

Create a Bitbucket credential

Choose the method that matches your Bitbucket edition:

Bitbucket Cloud - App Password:

Go to bitbucket.org/account/settings/app-passwords/new
Label: e.g., "Rensei"
Permissions:
- Repositories: Read and Repositories: Write - repository access
- Issues: Read and Issues: Write - for future issue tracker support
Copy the App Password

Bitbucket Server / Data Center - Personal Access Token:

Go to your instance → Settings → Account settings → Personal access tokens
Click Create a token
Permissions: REPO_READ, REPO_WRITE
Copy the token

Add the credential to Rensei

In Rensei, go to Settings → Integrations (or bind during project setup)
Select Bitbucket as the repository provider
Paste your App Password or Personal Access Token
For Bitbucket Server / Data Center, enter your instance URL: https://bitbucket.mycompany.com
Click Connect

The platform validates the credential and stores it encrypted.

Current repository binding

When you bind a Bitbucket repository to a Rensei project:

Workflows can reference {{ $repo.file }} to read repository content
Agents can commit code and push branches
Generic git nodes (branch creation, file operations) work with Bitbucket

Example workflow with Bitbucket:

steps:
  - id: read_readme
    type: github.file.read  # Works with Bitbucket too
    inputs:
      repo: "myproject/myrepo"
      path: "README.md"

  - id: update_docs
    type: github.file.create
    inputs:
      repo: "myproject/myrepo"
      path: "docs/api.md"
      contents: "{{ $steps.agent.output }}"
      branch: "feature/docs-{{ $workflow.id }}"
      message: "Updated API docs"

Issue tracker (coming soon)

Once the Bitbucket issue tracker is fully implemented, you will be able to:

Create Bitbucket issues from workflows
Search and update issues
Post comments
Transition issues through Bitbucket workflows

Track progress on the coverage matrix.

Bitbucket Cloud vs Server vs Data Center

Rensei supports all three Bitbucket editions:

Edition	Setup	Notes
Bitbucket Cloud	App Password	Hosted by Atlassian; simplest setup
Bitbucket Server	Personal Access Token + instance URL	Self-hosted; older version (deprecated by Atlassian)
Bitbucket Data Center	Personal Access Token + instance URL	Self-hosted; modern, clustering support

Limitations

Issue tracker: Not yet supported; use Linear, Jira, or Asana
Webhooks: Repository events are received but not yet exposed as workflow triggers
Pull requests: PR operations are not yet exposed as workflow nodes
Deployments: Bitbucket Deployments are not yet integrated
Repository variables: Bitbucket repository variables cannot yet be accessed in workflows

Troubleshooting

"Authentication failed"

Verify your App Password or Personal Access Token is still valid
Check the credential has not been revoked in Bitbucket
Ensure the credential has the required permissions (REPO_READ, REPO_WRITE)
For Bitbucket Server, verify your instance URL is correct

"Repository not found"

Verify the repository path is correct (e.g., myproject/myrepo)
Ensure you have access to the repository in Bitbucket
For Bitbucket Server, verify the instance URL matches your Bitbucket instance

"Permission denied"

Check that your App Password or Personal Access Token has repository:write permissions
Verify your Bitbucket user account has write access to the target repository

Next steps

GitHub integration - For repository operations today
Repository binding - Bind Bitbucket repos to Rensei projects
Workflow triggers - Set up event-based automation
Check back soon for full Bitbucket issue tracker support

On this page