Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2022-01-25 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-12-22 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2021-02-12 | 1 | -0/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2019-12-22 | 1 | -0/+2 |
| | |||||
* | Remove unneeded monkey-patch54478-table_exists-not-compatible-with-rails-5-1 | Heinrich Lee Yu | 2019-07-25 | 1 | -4/+0 |
| | | | | | Changes all calls to data_source_exists? to table_exists? since that is the intent of these calls | ||||
* | Document ApplicationRecord / pluck_primary_key | Nick Thomas | 2019-03-29 | 1 | -1/+1 |
| | | | | We also enable the rubocop that makes it mandatory | ||||
* | Batch insert CI rspec_profiling data | Stan Hu | 2019-03-12 | 1 | -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 |