Skip to content

Mark ci_runner_versions as exempt_from_sharding

Pedro Pombeiro requested to merge pedropombeiro/460096/mark-ci_runner_versions-exempt_from_sharding into master

What does this MR do and why?

I'm marking the ci_runner_versions table as exempt_from_sharding because this table is being used as a cache that gets filled by the Ci::Runners::ProcessRunnerVersionUpdateWorker whenever a runner manager's version changes. This data is being used to show in the admin runners list which ones are out-of-date.

Important note: Whenever we move an organization to a different cell, we should call Ci::Runners::ProcessRunnerVersionUpdateWorker with the versions of the moved runners, so that ci_runner_versions in the target cell is ensured to be populated with the necessary versions (I'll create a follow-up issue for that if this gets merged).

Part of #460096 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

n/a

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

n/a

Edited by Pedro Pombeiro

Merge request reports