Cross recovery options
This article describes the cross recovery options in Bitbucket
Cross recovery options
In general, GitProtect allows you to restore the data between GitHub, GitLab and Bitbucket. Different vendors give you an opportunity to create different metadata, which is not common to all providers. Due to this fact, during the restore process, you can meet the case, when some metadata may be not available to restore. In this article, you will find the information, on which metadata is allowed to restore between Bitbucket and other Git providers.
See also the article with Bitbucket protected metadata:
Protected Bitbucket Resources / Elements / MetadataMetadata | Restore to |
---|---|
Downloads | Bitbucket |
Deployment keys | Bitbucket, GitHub, GitHub Enterprise, GitLab |
Pull requests | Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab |
Pull requests comments | Bitbucket, GitHub, GitHub Enterprise, GitLab |
Webhooks | Bitbucket |
Pipelines | Bitbucket |
Tag | Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab |
LFS | Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab |
Commits | Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab |
Issue Comments | Bitbucket, GitHub, GitHub Enterprise, GitLab |
Issues | Bitbucket, GitHub, GitHub Enterprise, GitLab |
Repository | Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab |
Wiki | Bitbucket, GitHub, GitHub Enterprise, GitLab |
Branches | Bitbucket, Bitbucket DC, GitHub, GitHub Enterprise, GitLab |
Pipeline schedules | Bitbucket |
Pipeline known hosts | Bitbucket |
Branching model | Bitbucket |
Branch restrictions | Bitbucket |
Last updated