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.
24 lines
899 B
Text
24 lines
899 B
Text
- page_title _("GitLab Import")
|
|
- header_title _("Projects"), root_path
|
|
|
|
%h3.page-title
|
|
= icon('gitlab')
|
|
= _('Import an exported GitLab project')
|
|
%hr
|
|
|
|
= form_tag import_gitlab_project_path, class: 'new_project', multipart: true do
|
|
= render 'import/shared/new_project_form'
|
|
|
|
.row
|
|
.form-group.col-md-12
|
|
= _("To move or copy an entire GitLab project from another GitLab installation to this one, navigate to the original project's settings page, generate an export file, and upload it here.")
|
|
.row
|
|
.form-group.col-sm-12
|
|
= hidden_field_tag :namespace_id, @namespace.id
|
|
= label_tag :file, _('GitLab project export'), class: 'label-bold'
|
|
.form-group
|
|
= file_field_tag :file, class: ''
|
|
.row
|
|
.form-actions.col-sm-12
|
|
= submit_tag _('Import project'), class: 'btn btn-success'
|
|
= link_to _('Cancel'), new_project_path, class: 'btn btn-cancel'
|