Move ExecuteBuildHooksWorker to continuous_integration feature category
What does this MR do and why?
Changes the feature category of Ci::ExecuteBuildHooksWorker from pipeline_composition to continuous_integration, moving it from Pipeline Authoring to Pipeline Execution.
The worker was added in !177706 (merged) as part of pipeline creation performance work, which is why it was tagged pipeline_composition. What it does today is send job event webhooks and job-hook integrations when a job changes status. Ci::Build#execute_hooks queues it when:
- a job moves to
pending - a job starts running (
pending→running) - a job finishes, through
Ci::BuildFinishedWorker - a job is created outside pipeline creation, for example on retry
Those are job runtime events, and the code paths they come from (BuildQueueWorker, Ci::BuildPrepareWorker, Ci::BuildFinishedWorker) are already continuous_integration.
Job hooks sent during pipeline creation now go through a separate worker, Ci::ExecutePipelineBuildHooksWorker, queued by the Gitlab::Ci::Pipeline::Chain::TriggerBuildHooks chain step. That worker stays pipeline_composition.
This is a metadata change only. Worker behaviour, queue name and urgency are unchanged.
References
- !177706 (merged) added the worker
- #499290 (closed), the pipeline creation performance work it was part of
How to set up and validate locally
No behaviour change. bundle exec rake gitlab:sidekiq:queues:check passes with the updated app/workers/all_queues.yml.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.