summaryrefslogtreecommitdiff
path: root/scripts/insert-rspec-profiling-data
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2022-01-251-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-12-221-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-02-121-0/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-12-221-0/+2
|
* Remove unneeded monkey-patch54478-table_exists-not-compatible-with-rails-5-1Heinrich Lee Yu2019-07-251-4/+0
| | | | | Changes all calls to data_source_exists? to table_exists? since that is the intent of these calls
* Document ApplicationRecord / pluck_primary_keyNick Thomas2019-03-291-1/+1
| | | | We also enable the rubocop that makes it mandatory
* Batch insert CI rspec_profiling dataStan Hu2019-03-121-0/+47
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