diff options
| author | Bob Van Landuyt <bob@vanlanduyt.co> | 2019-04-23 16:27:01 +0200 |
|---|---|---|
| committer | Bob Van Landuyt <bob@vanlanduyt.co> | 2019-05-31 09:40:54 +0200 |
| commit | 589b2db06ca2ca2bc3e5d9e56968e3609f9e4626 (patch) | |
| tree | 1652ec910b83d71666fabcf1957d46886a400d40 /doc/user/project/import/index.md | |
| parent | 6189c869b87aa469f5efb058834cd65afd8fe563 (diff) | |
| download | gitlab-ce-589b2db06ca2ca2bc3e5d9e56968e3609f9e4626.tar.gz | |
Setup Phabricator import
This sets up all the basics for importing Phabricator tasks into
GitLab issues.
To import all tasks from a Phabricator instance into GitLab, we'll
import all of them into a new project that will have its repository
disabled.
The import is hooked into a regular ProjectImport setup, but similar
to the GitHub parallel importer takes care of all the imports itself.
In this iteration, we're importing each page of tasks in a separate
sidekiq job.
The first thing we do when requesting a new page of tasks is schedule
the next page to be imported. But to avoid deadlocks, we only allow a
single job per worker type to run at the same time.
For now we're only importing basic Issue information, this should be
extended to richer information.
Diffstat (limited to 'doc/user/project/import/index.md')
| -rw-r--r-- | doc/user/project/import/index.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md index ebbc5ca133b..119bbbfc70b 100644 --- a/doc/user/project/import/index.md +++ b/doc/user/project/import/index.md @@ -14,6 +14,7 @@ 1. [From repo by URL](repo_by_url.md) 1. [By uploading a manifest file (AOSP)](manifest.md) 1. [From Gemnasium](gemnasium.md) +1. [From Phabricator](phabricator.md) In addition to the specific migration documentation above, you can import any Git repository via HTTP from the New Project page. Be aware that if the |