1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
---
stage: none
group: unassigned
info: Any user with at least the Maintainer role can merge updates to this content. For details, see https://docs.gitlab.com/ee/development/development_processes.html#development-guidelines-review.
---
# Bitbucket Cloud importer developer documentation
## Prerequisites
You must be authenticated with Bitbucket:
- If you use GitLab Development Kit (GDK), see [Set up Bitbucket authentication on GDK](#set-up-bitbucket-authentication-on-gdk).
- Otherwise, see [Bitbucket OmniAuth provider](../integration/bitbucket.md#use-bitbucket-as-an-oauth-20-authentication-provider) instructions.
## Code structure
The importer's codebase is broken up into the following directories:
- `lib/gitlab/bitbucket_import`: this directory contains most of the code such as
the classes used for importing resources.
- `app/workers/gitlab/bitbucket_import`: this directory contains the Sidekiq
workers.
## Architecture overview
When a Bitbucket Cloud project is imported, work is
divided into separate stages, with each stage consisting of a set of Sidekiq
jobs that are executed. Between every stage, a job is scheduled that periodically
checks if all work of the current stage is completed, advancing the import
process to the next stage when this is the case. The worker handling this is
called `Gitlab::BitbucketImport::AdvanceStageWorker`.
## Stages
### 1. Stage::ImportRepositoryWorker
This worker imports the repository, wiki and labels, scheduling the next stage when
done.
### 2. Stage::ImportPullRequestsWorker
This worker imports all pull requests. For every pull request, a job for the
`Gitlab::BitbucketImport::ImportPullRequestWorker` worker is scheduled.
### 3. Stage::ImportPullRequestsNotesWorker
This worker imports notes (comments) for all merge requests.
For every merge request, a job for the `Gitlab::BitbucketImport::ImportPullRequestNotesWorker` worker is scheduled which imports all notes for the merge request.
### 4. Stage::ImportIssuesWorker
This worker imports all issues. For every issue, a job for the
`Gitlab::BitbucketImport::ImportIssueWorker` worker is scheduled.
### 5. Stage::ImportIssuesNotesWorker
This worker imports notes (comments) for all issues.
For every issue, a job for the `Gitlab::BitbucketImport::ImportIssueNotesWorker` worker is scheduled which imports all notes for the issue.
### 5. Stage::FinishImportWorker
This worker completes the import process by performing some housekeeping
such as marking the import as completed.
## Set up Bitbucket authentication on GDK
To set up Bitbucket authentication on GDK:
1. Follow the documentation up to step 9 to create
[Bitbucket OAuth credentials](../integration/bitbucket.md#use-bitbucket-as-an-oauth-20-authentication-provider).
1. Add the credentials to `config/gitlab.yml`:
```yaml
# config/gitlab.yml
development:
<<: *base
omniauth:
providers:
- { name: 'bitbucket',
app_id: '...',
app_secret: '...' }
```
1. Run `gdk restart`.
1. Sign in to your GDK, go to `<gdk-url>/-/profile/account`, and connect Bitbucket.
|
