Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Migration from Bitbucket Data Center to Bitbucket Cloud is supported with some limitations. Contact us when you have a scenario that is not directly supported.

Feature Comparison

Feature

Bitbucket Server/Data Center

Bitbucket Cloud

Code Owner Rules with Users

(tick)

(tick) Only Display or Nickname Supported. Email is not supported.

Code Owner Rules with Groups

(tick)

(tick) Only Groups defined in the Code Owner files are supported. Bitbucket Groups are not supported

Merge Checks

(tick)

(tick) Failed Merge Checks appear as failed builds and are shown in a Web Card.

Separate Code Owners File in sub directories (For mono repos)

(tick)

(error)

Branch Filters

(tick)

(error)

Migration Guide from Server/Data Center to Cloud

  1. If you are referencing Bitbucket groups in the Code Owner file, like * @@BitbucketGroup, then add a group definition in the Code Owners file with its members, like so @@@BitBucketGroup @"Member One" @"Member Two". Because the Cloud version does not yet support Bitbucket groups.

  2. Replace emails and user names with display names. The Cloud edition only supports display and nick names. Therefore, replace an email like * jordan@example.local with * @"Jordan Example".

  3. If you have merge checks, enable the Minimal Successful Builds in the Bitbucket Cloud merge checks, as failed merge checks appear as failed builds.

  4. If you have Code Owners file for different sub-directories, then you have to consolidate the rules in the top-level Code Owners file. Let us know if want support for multiple Code Owners files on Bitbucket Cloud.

  5. Branch filters are not supported. If you need branch filter in the Cloud, let us know.

  • No labels