Ignore ci_trigger_requests.variables column
What does this MR do and why?
Since 75130a41 and
!91576 (merged), we no
longer save any data to ci_trigger_requests.variables
and instead
save key/value pairs in ci_pipeline_variables
. Ignore the
ci_trigger_request.variables
column since it has not been used in
years. It appears on some old jobs, an empty Hashie::Mash
is
serialized, which causes a 500 error when viewing the job since it's
not a permitted class for YAML.safe_load
.
Relates to #440216 (closed)
Edited by Stan Hu