gitlab-org--gitlab-foss/app/workers/project_export_worker.rb

class ProjectExportWorker
  include ApplicationWorker
  include ExceptionBacktrace

  sidekiq_options retry: 3

  def perform(current_user_id, project_id, after_export_strategy = {}, params = {})
    current_user = User.find(current_user_id)
    project = Project.find(project_id)
    after_export = build!(after_export_strategy)

    ::Projects::ImportExport::ExportService.new(project, current_user, params).execute(after_export)
  end

  private

  def build!(after_export_strategy)
    strategy_klass = after_export_strategy&.delete('klass')

    Gitlab::ImportExport::AfterExportStrategyBuilder.build!(strategy_klass, after_export_strategy)
  end
end
add export worker to process project export async 2016-05-04 04:59:33 -04:00			`class ProjectExportWorker`
Add ApplicationWorker and make every worker include it 2017-11-28 11:08:30 -05:00			`include ApplicationWorker`
Enable 5 lines of Sidekiq backtrace lines to aid in debugging Customers often have Sidekiq jobs that failed without much context. Without Sentry, there's no way to tell where these exceptions were hit. Adding in additional lines adds a bit more Redis storage overhead. This commit adds in backtrace logging for workers that delete groups/projects and import/export projects. Closes #27626 2017-08-24 15:24:58 -04:00			`include ExceptionBacktrace`
add export worker to process project export async 2016-05-04 04:59:33 -04:00
Re-organize queues to use for Sidekiq Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370 2016-10-21 12:13:41 -04:00			`sidekiq_options retry: 3`
add export worker to process project export async 2016-05-04 04:59:33 -04:00
Extend API for exporting a project with direct upload URL 2018-03-30 11:45:59 -04:00			`def perform(current_user_id, project_id, after_export_strategy = {}, params = {})`
add export worker to process project export async 2016-05-04 04:59:33 -04:00			`current_user = User.find(current_user_id)`
			`project = Project.find(project_id)`
Extend API for exporting a project with direct upload URL 2018-03-30 11:45:59 -04:00			`after_export = build!(after_export_strategy)`
adding notifications stuff and more refactoring for exporting projects 2016-06-14 10:31:03 -04:00
Extend API for exporting a project with direct upload URL 2018-03-30 11:45:59 -04:00			`::Projects::ImportExport::ExportService.new(project, current_user, params).execute(after_export)`
			`end`

			`private`

			`def build!(after_export_strategy)`
			`strategy_klass = after_export_strategy&.delete('klass')`

			`Gitlab::ImportExport::AfterExportStrategyBuilder.build!(strategy_klass, after_export_strategy)`
add export worker to process project export async 2016-05-04 04:59:33 -04:00			`end`
			`end`