Commit graph

10 commits

Author SHA1 Message Date
GitLab Bot
eef3d92529 Add latest changes from gitlab-org/gitlab@master 2022-06-08 21:08:52 +00:00
GitLab Bot
eb6b175049 Add latest changes from gitlab-org/gitlab@master 2022-05-31 15:09:02 +00:00
GitLab Bot
9ef26edc4a Add latest changes from gitlab-org/gitlab@master 2021-09-21 15:12:11 +00:00
GitLab Bot
21e144f387 Add latest changes from gitlab-org/gitlab@master 2021-06-07 18:10:23 +00:00
GitLab Bot
c3f28c9b07 Add latest changes from gitlab-org/gitlab@master 2021-04-27 18:10:02 +00:00
GitLab Bot
f5c3f32975 Add latest changes from gitlab-org/gitlab@master 2021-03-15 15:09:07 +00:00
GitLab Bot
3827baae07 Add latest changes from gitlab-org/gitlab@master 2020-08-13 00:10:06 +00:00
GitLab Bot
711f859532 Add latest changes from gitlab-org/gitlab@master 2020-06-01 15:08:16 +00:00
GitLab Bot
34e72e5412 Add latest changes from gitlab-org/gitlab@master 2020-05-21 18:08:27 +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