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

# frozen_string_literal: true

class PipelineHooksWorker # rubocop:disable Scalability/IdempotentWorker
  include ApplicationWorker

  sidekiq_options retry: 3
  include PipelineQueue

  queue_namespace :pipeline_hooks
  worker_resource_boundary :cpu
  data_consistency :delayed

  # rubocop: disable CodeReuse/ActiveRecord
  def perform(pipeline_id)
    Ci::Pipeline.includes({ builds: { runner: :tags } })
      .find_by(id: pipeline_id)
      .try(:execute_hooks)
  end
  # rubocop: enable CodeReuse/ActiveRecord
end
Enable frozen string literals for app/workers/*.rb 2018-06-27 03:23:28 -04:00			`# frozen_string_literal: true`

Add latest changes from gitlab-org/gitlab@master 2020-02-19 13:09:10 -05:00			`class PipelineHooksWorker # rubocop:disable Scalability/IdempotentWorker`
Add ApplicationWorker and make every worker include it 2017-11-28 11:08:30 -05:00			`include ApplicationWorker`
Add latest changes from gitlab-org/gitlab@master 2021-04-30 14:10:09 -04:00
			`sidekiq_options retry: 3`
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 PipelineQueue`
Execute pipeline hooks asynchronously 2016-10-12 07:44:33 -04:00
Use a dedicated queue for each worker 2017-11-28 11:16:50 -05:00			`queue_namespace :pipeline_hooks`
Add latest changes from gitlab-org/gitlab@master 2019-10-30 11:14:17 -04:00			`worker_resource_boundary :cpu`
Add latest changes from gitlab-org/gitlab@master 2021-06-17 14:10:22 -04:00			`data_consistency :delayed`
Assign all pipeline workers to specific queues 2017-08-21 08:02:20 -04:00
Disable existing offenses for the CodeReuse cops This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop. 2018-08-27 11:31:01 -04:00			`# rubocop: disable CodeReuse/ActiveRecord`
Execute pipeline hooks asynchronously 2016-10-12 07:44:33 -04:00			`def perform(pipeline_id)`
Add latest changes from gitlab-org/gitlab@master 2021-01-22 10:09:08 -05:00			`Ci::Pipeline.includes({ builds: { runner: :tags } })`
			`.find_by(id: pipeline_id)`
Execute pipeline hooks asynchronously 2016-10-12 07:44:33 -04:00			`.try(:execute_hooks)`
			`end`
Disable existing offenses for the CodeReuse cops This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop. 2018-08-27 11:31:01 -04:00			`# rubocop: enable CodeReuse/ActiveRecord`
Execute pipeline hooks asynchronously 2016-10-12 07:44:33 -04:00			`end`