delta/gitlab/gitlab-ce.git/scripts/insert-rspec-profiling-data, branch pack-refs gitlab.com: gitlab-org/gitlab-ce.git Document ApplicationRecord / pluck_primary_key 2019-03-29T20:54:06+00:00 Nick Thomas nick@gitlab.com 2019-03-29T11:23:05+00:00 98a5976b787fad0797bc5e3231c48ab3f400bce6 We also enable the rubocop that makes it mandatory 
We also enable the rubocop that makes it mandatory
Batch insert CI rspec_profiling data 2019-03-12T09:51:37+00:00 Stan Hu stanhu@gmail.com 2019-03-12T09:51:37+00:00 f11030173b909c64aa23ce7482af8fcee8554be9 Instead of inserting a row after each example to an external database, we save the CI profiling reports into the `rspec_profiling` directory and insert the data in the update-tests-metadata CI stage. This should make each spec run faster and also reduce the number of PostgreSQL connections needed by concurrent CI builds. `scripts/insert-rspec-profiling-data` also inserts one file at a time via the PostgreSQL COPY command for faster inserts. The one side effect is that the `created_at` and `updated_at` timestamps aren't available since they aren't generated in the CSV. Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/10154 
Instead of inserting a row after each example to an external database,
we save the CI profiling reports into the `rspec_profiling` directory
and insert the data in the update-tests-metadata CI stage.  This should
make each spec run faster and also reduce the number of PostgreSQL
connections needed by concurrent CI builds.

`scripts/insert-rspec-profiling-data` also inserts one file at a time
via the PostgreSQL COPY command for faster inserts. The one side effect
is that the `created_at` and `updated_at` timestamps aren't available
since they aren't generated in the CSV.

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/10154