diff options
| author | Steve Azzopardi <sazzopardi@gitlab.com> | 2019-07-02 11:22:03 +0200 |
|---|---|---|
| committer | Steve Azzopardi <sazzopardi@gitlab.com> | 2019-07-02 11:22:03 +0200 |
| commit | 2ce377658ee4275d9d62ff234a824a0e5c55c2af (patch) | |
| tree | cf4951272a29585946b7e67312598d43f091dad1 | |
| parent | 29b8830bf8ab7cfe37bc0f41066400509fff519f (diff) | |
| download | gitlab-ce-disable-junit-reports.tar.gz | |
Disable juint reports tmpdisable-junit-reports
The junit reports are creating 90mb files inside of redis for
`gitlab-ce/ee` project. There is an ongoing production incident
https://gitlab.com/gitlab-com/gl-infra/production/issues/928 that is
because of high CPU uitlaization on the redis nodes. GitLab-ce/ee are
the highest consumers of memory becuase of these junit reports.
This is a bandage until we can scale redis properly.
| -rw-r--r-- | .gitlab/ci/frontend.gitlab-ci.yml | 8 | ||||
| -rw-r--r-- | .gitlab/ci/rails.gitlab-ci.yml | 4 |
2 files changed, 6 insertions, 6 deletions
diff --git a/.gitlab/ci/frontend.gitlab-ci.yml b/.gitlab/ci/frontend.gitlab-ci.yml index 8314c067d7a..6e80cb530f1 100644 --- a/.gitlab/ci/frontend.gitlab-ci.yml +++ b/.gitlab/ci/frontend.gitlab-ci.yml @@ -168,8 +168,8 @@ karma: paths: - chrome_debug.log - coverage-javascript/ - reports: - junit: junit_karma.xml +# reports: +# junit: junit_karma.xml jest: extends: .dedicated-no-docs-and-no-qa-pull-cache-job @@ -191,8 +191,8 @@ jest: paths: - coverage-frontend/ - junit_jest.xml - reports: - junit: junit_jest.xml +# reports: +# junit: junit_jest.xml cache: key: jest paths: diff --git a/.gitlab/ci/rails.gitlab-ci.yml b/.gitlab/ci/rails.gitlab-ci.yml index 009c18310e4..9d24099b85c 100644 --- a/.gitlab/ci/rails.gitlab-ci.yml +++ b/.gitlab/ci/rails.gitlab-ci.yml @@ -77,8 +77,8 @@ - rspec_flaky/ - rspec_profiling/ - tmp/capybara/ - reports: - junit: junit_rspec.xml +# reports: +# junit: junit_rspec.xml .rspec-metadata-pg: &rspec-metadata-pg <<: *rspec-metadata |