Re-sync basic epic fields to work items
We re-queue the backfill migration because we backfill the data in two steps: 1. The initial backfilling created a work item for every epic to unblock any follow-up migrations that depend on the work item data. At the time we ran the migration, we did not sync epic to work item data by default in the application layer. 2. The second backfilling (this one) re-syncs the data again to make sure it's up to date. At this time we enabled syncing epic to work item data already by default. Changelog: changed
显示
- db/docs/batched_background_migrations/resync_basic_epic_fields_to_work_item.yml 12 个添加, 0 个删除...ound_migrations/resync_basic_epic_fields_to_work_item.yml
- db/post_migrate/20240528112758_queue_resync_basic_epic_fields_to_work_item.rb 36 个添加, 0 个删除...0528112758_queue_resync_basic_epic_fields_to_work_item.rb
- db/schema_migrations/20240528112758 1 个添加, 0 个删除db/schema_migrations/20240528112758
- lib/gitlab/background_migration/backfill_epic_basic_fields_to_work_item_record.rb 1 个添加, 1 个删除...gration/backfill_epic_basic_fields_to_work_item_record.rb
- lib/gitlab/background_migration/resync_basic_epic_fields_to_work_item.rb 12 个添加, 0 个删除...ground_migration/resync_basic_epic_fields_to_work_item.rb
- spec/lib/gitlab/background_migration/resync_basic_epic_fields_to_work_item_spec.rb 98 个添加, 0 个删除...d_migration/resync_basic_epic_fields_to_work_item_spec.rb
- spec/migrations/20240528112758_queue_resync_basic_epic_fields_to_work_item_spec.rb 27 个添加, 0 个删除...12758_queue_resync_basic_epic_fields_to_work_item_spec.rb
加载中
想要评论请 注册 或 登录