Timothy Andrew 161804bf40 Add a "populate metrics directly" option to the cycle analytics seed. ... - The normal seed creates all the data for cycle analytics the "right" way. It creates issues, merge requests, commits, branches, deployments, etc. This is good, but too slow for perf testing. Generating a 1000 sets of records this way takes more than an hour. - When the `CYCLE_ANALYTICS_POPULATE_METRICS_DIRECTLY` environment variable is passed in, the seed only creates issues and merge requests. It then adds the `metrics` for each issue and merge request directly, to save time. - The seed now takes about 4 minutes to run for 1000 sets of records.		2016-09-17 12:16:48 +05:30
..
01_admin.rb
04_project.rb	Remove project which can't be pulled while seeding	2016-07-28 20:00:04 +02:00
05_users.rb
06_teams.rb
07_milestones.rb	Fix seed_fu failure with inserting milestones into test DB	2016-04-10 06:39:42 -07:00
09_issues.rb
10_merge_requests.rb	Limit the number of merge requests per project to avoid long seeds	2016-05-04 09:22:01 -07:00
11_keys.rb
12_snippets.rb
13_comments.rb
14_pipelines.rb	Move and improvement comment in pipeline fixtures	2016-08-19 14:43:02 +02:00
15_award_emoji.rb	Random selection now also works for MySQL	2016-06-15 12:10:41 +02:00
16_protected_branches.rb	Add seeds for protected branches.	2016-07-29 15:20:39 +05:30
17_cycle_analytics.rb	Add a "populate metrics directly" option to the cycle analytics seed.	2016-09-17 12:16:48 +05:30