Cascade partition_id value to more resources
Description
Following up !103594 (merged) where we introduced partition_id
to CI models referenced by foreign keys (required to partition ci_builds
).
We now need to cascade partition_id
to those tables before inserting new data to our second partition otherwise those records would point to the wrong builds.
Technical proposal
Table | MR |
---|---|
ci_unit_test_failures |
!104571 (merged) |
ci_sources_pipelines |
!104678 (merged) |
ci_resources (added partition_id in !104567 (merged)) |
!104683 (closed), !106431 (merged) |
ci_build_pending_states |
!104695 (merged) |
ci_build_trace_chunks |
!104836 (merged) |
ci_build_report_results |
!104834 (merged) |
ci_build_needs |
!104953 (merged) |
ci_builds_runner_session |
!105520 (merged) |
ci_pending_builds |
!104718 (merged) @grzesiek |
ci_running_builds |
!104718 (merged) @grzesiek |
ci_build_trace_metadata |
!105314 (merged) |
ci_job_variables |
!105636 (merged) |
Here an example MR to accomplish this.
Edited by Max Orefice