debian-mirror-gitlab/doc/user/project/import/bitbucket.md

72 lines
3 KiB
Markdown
Raw Normal View History

2018-11-18 11:00:15 +05:30
# Import your project from Bitbucket Cloud to GitLab
2018-03-17 18:26:18 +05:30
2018-11-18 11:00:15 +05:30
NOTE: **Note:**
The Bitbucket Cloud importer works only with Bitbucket.org, not with Bitbucket
Server (aka Stash). If you are trying to import projects from Bitbucket Server, use
[the Bitbucket Server importer](bitbucket_server.md).
2018-03-17 18:26:18 +05:30
2018-11-18 11:00:15 +05:30
Import your projects from Bitbucket Cloud to GitLab with minimal effort.
2018-03-17 18:26:18 +05:30
2018-11-18 11:00:15 +05:30
## Overview
2018-11-08 19:23:39 +05:30
2018-03-17 18:26:18 +05:30
- At its current state, the Bitbucket importer can import:
- the repository description (GitLab 7.7+)
- the Git repository data (GitLab 7.7+)
- the issues (GitLab 7.7+)
- the issue comments (GitLab 8.15+)
- the pull requests (GitLab 8.4+)
- the pull request comments (GitLab 8.15+)
- the milestones (GitLab 8.15+)
- the wiki (GitLab 8.15+)
- References to pull requests and issues are preserved (GitLab 8.7+)
- Repository public access is retained. If a repository is private in Bitbucket
it will be created as private in GitLab as well.
2018-11-18 11:00:15 +05:30
## Requirements
2020-05-24 23:13:21 +05:30
The [Bitbucket Cloud integration](../../../integration/bitbucket.md) must be first enabled in order to be
2018-11-18 11:00:15 +05:30
able to import your projects from Bitbucket Cloud. Ask your GitLab administrator
to enable this if not already.
2018-03-17 18:26:18 +05:30
## How it works
When issues/pull requests are being imported, the Bitbucket importer tries to find
2019-10-12 21:52:04 +05:30
the Bitbucket author/assignee in GitLab's database using the Bitbucket `nickname`.
For this to work, the Bitbucket author/assignee should have signed in beforehand in GitLab
and **associated their Bitbucket account**. Their `nickname` must also match their Bitbucket
`username.`. If the user is not found in GitLab's database, the project creator
(most of the times the current user that started the import process) is set as the author,
but a reference on the issue about the original Bitbucket author is kept.
2018-03-17 18:26:18 +05:30
The importer will create any new namespaces (groups) if they don't exist or in
the case the namespace is taken, the repository will be imported under the user's
namespace that started the import process.
2020-05-24 23:13:21 +05:30
## Import your Bitbucket repositories
2018-03-17 18:26:18 +05:30
1. Sign in to GitLab and go to your dashboard.
1. Click on **New project**.
2018-11-18 11:00:15 +05:30
1. Click on the "Bitbucket Cloud" button.
2018-03-17 18:26:18 +05:30
2019-10-12 21:52:04 +05:30
![Bitbucket](img/import_projects_from_new_project_page.png)
2018-03-17 18:26:18 +05:30
1. Grant GitLab access to your Bitbucket account
2019-10-12 21:52:04 +05:30
![Grant access](img/bitbucket_import_grant_access.png)
2018-03-17 18:26:18 +05:30
1. Click on the projects that you'd like to import or **Import all projects**.
2019-12-21 20:55:43 +05:30
You can also filter projects by name and select the namespace under which
each project will be imported.
2018-03-17 18:26:18 +05:30
2019-12-21 20:55:43 +05:30
![Import projects](img/bitbucket_import_select_project_v12_3.png)
2018-03-17 18:26:18 +05:30
2020-05-24 23:13:21 +05:30
## Troubleshooting
If you have more than one Bitbucket account, be sure to sign in to the correct account.
If you've accidentally started the import process with the wrong account, follow these steps:
1. Revoke GitLab access to your Bitbucket account, essentially reversing the process in the following procedure: [Import your Bitbucket repositories](#import-your-bitbucket-repositories).
1. Sign out of the Bitbucket account. Follow the procedure linked from the previous step.