Udate db-patterns in CI to run when db_cleaner, load balancer changes
What does this MR do and why?
Recently we introduced a master broken issue in
#395718 (closed) which was due to a
change to spec/support/db_cleaner.rb
in
!113368 (merged) . We didn't
notice in CI because we never ran the migration specs on that MR. Since
these db_cleaner
changes can have wide ranging consequences I'm adding
these to .db-changes
which (if I understand the logic correctly)
should mean that we trigger all the DB related jobs to run (including
migration specs).
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.