Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

.gitlab-ci.yml

  • Stan Hu's avatar
    f1103017
    Batch insert CI rspec_profiling data · f1103017
    Stan Hu authored
    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
    f1103017
    History
    Batch insert CI rspec_profiling data
    Stan Hu authored
    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