Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

sidekiq_queues.yml

  • Bob Van Landuyt's avatar
    589b2db0
    Setup Phabricator import · 589b2db0
    Bob Van Landuyt authored
    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.
    589b2db0
    History
    Setup Phabricator import
    Bob Van Landuyt authored
    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.