diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-02 03:17:32 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-12-02 03:17:32 +0300 |
| commit | ef615776bf132cb0c56cafd51ac97fb1b7f26a58 (patch) | |
| tree | 6656732d3d9434300c6fcf4057254083c9b269eb /doc/development/pipelines.md | |
| parent | 7b78125a3829026f54bd87ab560758de3f37ad82 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/pipelines.md')
| -rw-r--r-- | doc/development/pipelines.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/development/pipelines.md b/doc/development/pipelines.md index a813502db51..36a5301de65 100644 --- a/doc/development/pipelines.md +++ b/doc/development/pipelines.md @@ -220,6 +220,20 @@ The `* as-if-jh` jobs are run in addition to the regular EE-context jobs. The `j The intent is to ensure that a change doesn't introduce a failure after the `gitlab-org/gitlab` project is synced to the `gitlab-jh/gitlab` project. +## `undercover` RSpec test + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74859) in GitLab 14.6. + +The `rspec:undercoverage` job runs [`undercover`](https://rubygems.org/gems/undercover) +to detect, and fail if any changes introduced in the merge request has zero coverage. + +The `rsepc:undercoverage` job obtains coverage data from the `rspec:coverage` +job. + +In the event of an emergency, or false positive from this job, add the +`pipeline:skip-undercoverage` label to the merge request to allow this job to +fail. + ## PostgreSQL versions testing Our test suite runs against PG12 as GitLab.com runs on PG12 and |