Skip to content

Seed all fixtures with Seeder

Nailia Iskhakova requested to merge tp-data-seeding-configuration-for-upgrades into master

What does this MR do and why?

First iteration on seeding all fixtures using Data Seeder and FactoryBot. Seeder file will be used to create PG Dumps for db:migrate:multi-version-upgrade

Note that some fixtures fail to be seeded (example), this will be iterated on as part of Expand data seeding configuration for multi-ver... (gitlab-org/quality/quality-engineering/team-tasks#2354 - closed). Most common errors seen in gitlab-org/quality/quality-engineering/team-tasks#2354 (comment 1772988958) are resolved with this MR.

Result of the seedings are:

  • Seeding all possible fixtures
  • Continue to seed minimum data with build_subgroups and build_super_group_labels

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Testing

✅ https://gitlab.com/gitlab-org/quality/pg-dump-generator/-/jobs/6270181897#L1305

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. In GDK run the command to seed the data 
    GITLAB_LOG_LEVEL=debug bundle exec rake "ee:gitlab:seed:data_seeder[bulk_data.rb]"

Alternatively - triggering [Manual] Force create PG dump for the custom Data Seeder file and GitLab repo branch (no commit, no report) in https://gitlab.com/gitlab-org/quality/pg-dump-generator/-/pipeline_schedules that runs PG Dump generator using code from this MR branch.

Edited by Nailia Iskhakova

Merge request reports