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

# frozen_string_literal: true

class PipelineScheduleWorker
  include ApplicationWorker
  include CronjobQueue

  feature_category :continuous_integration
  worker_resource_boundary :cpu

  def perform
    Ci::PipelineSchedule.runnable_schedules.preloaded.find_in_batches do |schedules|
      schedules.each do |schedule|
        Ci::PipelineScheduleService.new(schedule.project, schedule.owner).execute(schedule)
      end
    end
  end
end
Enable frozen string literals for app/workers/*.rb 2018-06-27 03:23:28 -04:00			`# frozen_string_literal: true`

Add Pipeline Schedules that supersedes experimental Trigger Schedule 2017-05-07 18:35:56 -04:00			`class PipelineScheduleWorker`
Add ApplicationWorker and make every worker include it 2017-11-28 11:08:30 -05:00			`include ApplicationWorker`
Add Pipeline Schedules that supersedes experimental Trigger Schedule 2017-05-07 18:35:56 -04:00			`include CronjobQueue`
Prevent concurrent execution of PipelineScheduleWorker Currently, PipelineScheduleWorker is fired in a short period on our production server. We can stop this behavior by locking the execution thread with in_lock method. 2019-04-27 23:27:08 -04:00
Add latest changes from gitlab-org/gitlab@master 2019-10-18 07:11:44 -04:00			`feature_category :continuous_integration`
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 2019-10-18 07:11:44 -04:00
Add Pipeline Schedules that supersedes experimental Trigger Schedule 2017-05-07 18:35:56 -04:00			`def perform`
Make pipeline schedule worker resilient Currently, pipeline schedule worker is unstable because it's sometimes killed by excessive memory consumption. In order to improve the performance, we add the following fixes: 1. next_run_at is always real_next_run, which means the value always takes into account of worker's cron schedule 1. Remove exlusive lock. This is already covered by real_next_run change. 1. Use RunPipelineScheduleWorker for avoiding memory killer. Memory consumption is spread to the multiple sidekiq worker. 2019-05-17 08:10:44 -04:00			`Ci::PipelineSchedule.runnable_schedules.preloaded.find_in_batches do \|schedules\|`
			`schedules.each do \|schedule\|`
			`Ci::PipelineScheduleService.new(schedule.project, schedule.owner).execute(schedule)`
Prevent concurrent execution of PipelineScheduleWorker Currently, PipelineScheduleWorker is fired in a short period on our production server. We can stop this behavior by locking the execution thread with in_lock method. 2019-04-27 23:27:08 -04:00			`end`
Add Pipeline Schedules that supersedes experimental Trigger Schedule 2017-05-07 18:35:56 -04:00			`end`
			`end`
			`end`