2018-08-08 17:59:46 -04:00
|
|
|
# Import your project from Bitbucket Cloud to GitLab
|
2017-08-16 07:05:13 -04:00
|
|
|
|
2018-08-09 04:57:49 -04:00
|
|
|
NOTE: **Note:**
|
2018-08-08 17:59:46 -04:00
|
|
|
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-06-25 03:56:05 -04:00
|
|
|
|
2018-08-09 04:57:49 -04:00
|
|
|
Import your projects from Bitbucket Cloud to GitLab with minimal effort.
|
|
|
|
|
|
|
|
## Overview
|
|
|
|
|
2017-08-16 07:05:13 -04:00
|
|
|
- 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-08-09 04:57:49 -04:00
|
|
|
## Requirements
|
|
|
|
|
|
|
|
The [Bitbucket Cloud integration][bb-import] must be first enabled in order to be
|
|
|
|
able to import your projects from Bitbucket Cloud. Ask your GitLab administrator
|
|
|
|
to enable this if not already.
|
2017-08-16 07:05:13 -04:00
|
|
|
|
|
|
|
## How it works
|
|
|
|
|
|
|
|
When issues/pull requests are being imported, the Bitbucket importer tries to find
|
|
|
|
the Bitbucket author/assignee in GitLab's database using the Bitbucket ID. For this
|
|
|
|
to work, the Bitbucket author/assignee should have signed in beforehand in GitLab
|
|
|
|
and **associated their Bitbucket account**. 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.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
## Importing your Bitbucket repositories
|
|
|
|
|
|
|
|
1. Sign in to GitLab and go to your dashboard.
|
|
|
|
1. Click on **New project**.
|
|
|
|
|
2018-08-08 17:59:46 -04:00
|
|
|
1. Click on the "Bitbucket Cloud" button.
|
2017-08-16 07:05:13 -04:00
|
|
|
|
|
|
|
![Bitbucket](img/import_projects_from_new_project_page.png)
|
|
|
|
|
|
|
|
1. Grant GitLab access to your Bitbucket account
|
|
|
|
|
|
|
|
![Grant access](img/bitbucket_import_grant_access.png)
|
|
|
|
|
|
|
|
1. Click on the projects that you'd like to import or **Import all projects**.
|
|
|
|
You can also select the namespace under which each project will be
|
|
|
|
imported.
|
|
|
|
|
|
|
|
![Import projects](img/bitbucket_import_select_project.png)
|
|
|
|
|
|
|
|
[bb-import]: ../../../integration/bitbucket.md
|
|
|
|
[social sign-in]: ../../profile/account/social_sign_in.md
|