Legacy Ci::Pipeline doesn't belong to Ci::Ref
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
We introduced Ci::Ref in !28338 (merged) that represents an object of a ref for pipelines. All pipelines must belong to at least one ci-ref, otherwise it should be considered as invalid status.
We should add an AR validation or DB constraint to make sure it's always present.
Approach
- Ship backfill migration
- Add an AR validation or DB constraint
- Wait until builds are archived
- etc
Edited by 🤖 GitLab Bot 🤖