Skip to content

Add tag_name column to ci_runner_taggings table

What does this MR do and why?

This MR adds a tag_name column to ci_runner_taggings table, so that we don't rely on the cell-local tags table. It also adds logic to populate and keep up to date the field, based on the value from tags.

NOTE: we had to rollback !205053 (merged) because a pre-existing query that was not fully qualified started breaking in Sidekiq nodes when the database schema added a second name field to the tables involved in the query. I'm choosing the boring solution of calling the new column tag_name instead of name to avoid the clash, and to ensure that we can deliver this before the required stop.

Changelog: other

References

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.

Merge request reports

Loading