6a18a411a3
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.
13 lines
393 B
Ruby
13 lines
393 B
Ruby
# frozen_string_literal: true
|
|
|
|
module Ci
|
|
class PipelineScheduleService < BaseService
|
|
def execute(schedule)
|
|
# Ensure `next_run_at` is set properly before creating a pipeline.
|
|
# Otherwise, multiple pipelines could be created in a short interval.
|
|
schedule.schedule_next_run!
|
|
|
|
RunPipelineScheduleWorker.perform_async(schedule.id, schedule.owner.id)
|
|
end
|
|
end
|
|
end
|