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

class ProjectDestroyWorker
  include Sidekiq::Worker
  include DedicatedSidekiqQueue
  include ExceptionBacktrace

  def perform(project_id, user_id, params)
    project = Project.find(project_id)
    user = User.find(user_id)

    ::Projects::DestroyService.new(project, user, params.symbolize_keys).execute
  rescue ActiveRecord::RecordNotFound => error
    logger.error("Failed to delete project (#{project_id}): #{error.message}")
  end
end
First pass at deleting projects in the background. 2016-01-22 14:13:37 -05:00			`class ProjectDestroyWorker`
			`include Sidekiq::Worker`
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			`include DedicatedSidekiqQueue`
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`
First pass at deleting projects in the background. 2016-01-22 14:13:37 -05:00
			`def perform(project_id, user_id, params)`
Add specs for ProjectDestroyWorker 2017-06-29 07:43:01 -04:00			`project = Project.find(project_id)`
First pass at deleting projects in the background. 2016-01-22 14:13:37 -05:00			`user = User.find(user_id)`

Fix skip_repo parameter being ignored when destroying a namespace When destroying a namespace, the `skip_repo` parameter is supposed to prevent the repository directory from being destroyed and allow the namespace after_destroy hook to run. If the namespace fails to be deleted for some reason, we could be left with repositories that are deleted with existing projects. 2016-08-03 19:45:06 -04:00			`::Projects::DestroyService.new(project, user, params.symbolize_keys).execute`
Refactors Project Destroy service and worker code 2017-07-06 09:43:07 -04:00			`rescue ActiveRecord::RecordNotFound => error`
Move exception handling to execute 2017-07-18 11:09:14 -04:00			`logger.error("Failed to delete project (#{project_id}): #{error.message}")`
First pass at deleting projects in the background. 2016-01-22 14:13:37 -05:00			`end`
			`end`