Set up Source Control with Bitbucket

🚧

Source Control with Bitbucket is available on on-premise deployments of Self-hosted Retool v2.105 or later.

With Source Control with Bitbucket, you can use pull requests on Bitbucket cloud to manage changes to your Retool applications.

Setup instructions

Disable git syncing

If you've enabled Git Syncing, disable it:

• In your docker.env file, set DISABLE_GIT_SYNCING=true and VERSION_CONTROL_LOCKED=false.
• In the Settings > Advanced tab in Retool, remove the repository URL and branch name from your Git Syncing configuration.

Prerequisites

This guide requires access to a Bitbucket account with permissions to create workspaces and repositories.

1. Create a Bitbucket app password

1. Create a Bitbucket app password.
2. On the app password page under Permissions > Repositories, select Read, Admin, and Delete. This gives the app password the ability to access and modify the repository containing your Retool apps.

2. Create a new Bitbucket workspace and repository

1. Create a Bitbucket workspace for your Retool repository.
2. Create a Git repository in Bitbucket for your Retool apps.

3. Set up environment variables on your Retool instance

Set the following environment variables on your Retool instance.

4. Test your configuration

Once you set up your environment variables, if you’re an admin on your Retool instance, you can visit Settings > Source Control.

If your Bitbucket environment is correctly configured, the page will show your Bitbucket commits in the Deployment Dashboard section. You can also click the Test connection button, which sends a request to test the connection.

If you don't see the Deployment Dashboard and your Bitbucket commits on Settings > Source Control, check that your environment variables are correctly configured.

What's next?

You are now ready to use source control. Learn how to create branches, pull requests, merging changes, and use other source control features in the getting started guide.