Wercker continues to support new and existing applications which use Bitbucket. However on 1st April 2019 we are changing the way that Bitbucket applications are created and managed in Wercker.
The Add a new new application wizard will no longer 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.
Existing Wercker applications that use Bitbucket will be automatically converted from “Bitbucket” applications to “Other Git” applications. Builds will continue to work as they do now and users do not need to do anything.
Bitbucket applications currently offer a “report to SCM” feature which sends the status of a particular pipeline run to Bitbucket. The Bitbucket UI can then display the “build status” for a particular commit in the commit list and any pull request to merge the commit.
“Other Git” applications do not offer this feature.
The application “options” tab provides a number of features for managing the application. These features are slightly different for “Other Git” applications when compared to existing Bitbucket applications.
Bitbucket applications currently offer a “Fix webhook” button to automatically recreate the repository webhook. “Other Git” applications do not offer this feature. Instead they offer 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.
For Bitbucket applications the “Configure repository access” button can 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.
For “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.
This option allows you to change the repository used by your Wercker application. It will no longer offer Bitbucket as an option in the list of possible SCM providers. Instead if you wish to change an existing application that uses a Bitbucket repository you will need to choose “Other Git” and follow the instructions.