Loading
Consume the routed runner machine when assigning jobs
Related MRs
- !244035 (merged) - schema + read-side groundwork
- !247560 (merged) - persist
Ci::JobRuntimeEnvironmenton suspend - !247561 (merged) - record the runner machine assignment when a build starts running
- !247562 (merged) - resolve
runner_machine_idwhen queuing a suspend/resume build - This MR - consume the routed runner machine when assigning jobs
- !247564 (merged) - retire the old
environment_keystring-matching routing mechanism
What does this MR do and why?
Reads suspend_options (suspend_on_success, suspend_on_failure, environment_key) from the build's Ci::JobRuntimeEnvironment row instead of build.options.
Part of routing resumed builds to the runner machine that holds their suspended environment Resumable Jobs for CI and Agent Sessions (gitlab-org#21159).
References
Issue: Resumable Jobs for CI and Agent Sessions (gitlab-org#21159)
Blueprint: Add blueprint for suspendable environments (gitlab-com/content-sites/handbook!18954 - merged)
How to set up and validate locally
There is no E2E tests for this. Running spec would validate it.
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.
Edited by Ashvin Sharma