Changes to Bitbucket Support

Wercker continues to support new and existing applications which use Bitbucket. However on 1st April 2019 we changed the way that Bitbucket applications are created and managed in Wercker.

Changes to the “Add a new new application” wizard

The Add a new new application wizard no longers offer Bitbucket as an option in the list of possible SCM providers. Instead if you wish to create an application that uses a Bitbucket repository you should choose “Other Git” and follows the instructions.

The wizard will prompt you to enter the Git URL for your repository.

It will then display a webhook URL. You will need to visit your repository’s settings page on the Bitbucket website and manually add this URL.

The wizard will also display a generated SSH key. If your repository requires a SSH key to allow Wercker runs to access it you will need to upload this key manually by visiting your repository’s settings page.

Add Application Wizard Step 1

Existing applications have been automatically converted

Wercker applications that use Bitbucket which were created prior to this change have been automatically converted from “Bitbucket” applications to “Other Git” applications. Builds will continue to run as they do now and users do not need to do anything.

Pipelines will no longer report status to BitBucket

Prior to this change, Bitbucket applications offered a “report to SCM” feature which sent the status of a particular pipeline run to Bitbucket. The Bitbucket UI could then display the “build status” for a particular commit in the commit list and any pull request to merge the commit.

Now that Bitbucket applications are treated as “Other Git” applications, this feature is not available.

Changes to the “options” tab for a Bitbucket application

The application “options” tab provides a number of features for managing the application. Following the conversion of Bitbucket applications to “Other Git” applications a number of features have changed.

Fix Webhook

Prior to this change, Bitbucket applications offered a “Fix webhook” button to automatically recreate the repository webhook.

Now that Bitbucket applications are treated as “Other Git” applications, this feature is not available. Instead there is a “Show webhook” button which displays the required webhook URL. If you need need to re-create the repository webhook you will need to do so by visiting your repository’s settings page on the Bitbucket website and adding this URL.

Configure Repository Access

Prior to this change, Bitbucket applications offered a “Configure repository access” button which could be used to generate a SSH key and upload it automatically to the repository in order to give your Wercker runs access to your repository.

Now that Bitbucket applications are treated as “Other Git” applications, the “configure repository access” simply displays the generated SSH key. You will then need to upload it manually by visiting your repository’s settings page on the Bitbucket website.

Sync Wercker application

This option allows you to change the repository used by your Wercker application. It no longer offers Bitbucket as an option in the list of possible SCM providers. If you wish to change a application that uses a Bitbucket repository you need to choose “Other Git” and follow the instructions.