🔗 Improved Bitbucket Data Center integration

Changelog Website
, ,
1

Bitrise now properly integrates with self-hosted Bitbucket Server instances. If you’ve been running Bitbucket Server projects on Bitrise, you’ve likely been working around integration limitations that prevented you from using newer Bitrise features.

:relieved_face: What this fixes

Previously, Bitbucket Server projects on Bitrise couldn’t access features that require repository integration. You were stuck with basic build triggering and had to manually configure webhooks, SSH keys, and build status reporting through workarounds.

:smiling_cat_with_heart_eyes: What you get with the integration

Once enabled, Bitrise can interact with your Bitbucket Server instance the same way it does with cloud-hosted git providers:

  • Repository-stored configuration: keep your bitrise.yml in your repo alongside your code, with support for modular YAML on applicable plans
  • Automatic build status: build results post directly to Bitbucket Server without custom step configuration
  • PR comments: failed builds automatically comment on pull requests with error details
  • Advanced triggers: filter builds by changed files, commit message patterns, or PR comments
  • PR environment variables: access PR-specific data in your build environment
  • Automatic setup: SSH keys and webhooks configure themselves

:guide_dog: How to set it up

New projects

  • If you’re adding a brand new project to Bitrise, follow the steps on our docs here.

Existing projects

  1. Follow the setup guide to connect the workspace to Bitbucket Server.
    This needs to be done only once per workspace.
  2. Sign in to Bitrise with the user you want to use as the service credential user.
  3. On the Workspace Settings / Integrations page, click on the Bitbucket Server card.
  4. In the Authorize your user box, click Authorize (if not done already). This will open an authorization page on Bitbucket Server.

Review the permissions and click Allow.

  1. The Migrate repositories box below lists all CI projects in the workspace that has no integration enabled with any supported git provider. Select those that should be migrated.
  2. Click Migrate selected projects. This will enable the Bitbucket Server integration and set the current user as service credential user for all selected projects.
  3. The migrated projects now have multiple new features and configuration options.

Quick suggestion
Before proceeding, it is recommended to check if the setup works as expected by creating a new project using the Bitbucket Server integration before migrating existing projects.

Let us know if you encounter any issues. Happy building :waving_hand: