589b2db06c
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.
27 lines
812 B
Ruby
27 lines
812 B
Ruby
# frozen_string_literal: true
|
|
|
|
# The original import JID is the JID of the RepositoryImportWorker job,
|
|
# which will be removed once that job completes. Reusing that JID could
|
|
# result in StuckImportJobsWorker marking the job as stuck before we get
|
|
# to running Stage::ImportRepositoryWorker.
|
|
#
|
|
# We work around this by setting the JID to a custom generated one, then
|
|
# refreshing it in the various stages whenever necessary.
|
|
module Gitlab
|
|
module Import
|
|
module SetAsyncJid
|
|
def self.set_jid(project)
|
|
jid = generate_jid(project)
|
|
|
|
Gitlab::SidekiqStatus
|
|
.set(jid, StuckImportJobsWorker::IMPORT_JOBS_EXPIRATION)
|
|
|
|
project.import_state.update_column(:jid, jid)
|
|
end
|
|
|
|
def self.generate_jid(project)
|
|
"async-import/#{project.id}"
|
|
end
|
|
end
|
|
end
|
|
end
|