Commit graph

10 commits

Author SHA1 Message Date
GitLab Bot
87e9d9675a Add latest changes from gitlab-org/gitlab@master 2021-06-23 21:08:33 +00:00
GitLab Bot
9882aeb510 Add latest changes from gitlab-org/gitlab@master 2021-06-08 21:10:05 +00:00
GitLab Bot
66e86bca7a Add latest changes from gitlab-org/gitlab@master 2021-04-28 21:10:01 +00:00
GitLab Bot
a5605d87fb Add latest changes from gitlab-org/gitlab@master 2021-04-13 18:11:28 +00:00
GitLab Bot
b08b3719a1 Add latest changes from gitlab-org/gitlab@master 2021-03-08 21:09:45 +00:00
GitLab Bot
6e320396b2 Add latest changes from gitlab-org/gitlab@master 2020-10-26 12:08:44 +00:00
GitLab Bot
0c85feba3d Add latest changes from gitlab-org/gitlab@master 2020-09-26 00:09:35 +00:00
GitLab Bot
1c8fa70f9d Add latest changes from gitlab-org/gitlab@master 2020-02-28 18:09:07 +00:00
GitLab Bot
50ae406553 Add latest changes from gitlab-org/gitlab@master 2020-01-30 12:08:54 +00:00
Bob Van Landuyt
589b2db06c 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.
2019-05-31 09:40:54 +02:00