15 lines
1.4 KiB
YAML
15 lines
1.4 KiB
YAML
|
- name: "Test coverage project CI/CD setting" # The name of the feature to be deprecated
|
|||
|
|
announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
|
|||
|
|
announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
|
|||
|
|
removal_milestone: "15.0" # The milestone when this feature is planned to be removed
|
|||
|
|
removal_date: "2022-05-22" # The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
|
|||
|
|
breaking_change: true # If this deprecation is a breaking change, set this value to true
|
|||
|
|
reporter: jreporter # GitLab username of the person reporting the deprecation
|
|||
|
|
body: | # Do not modify this line, instead modify the lines below.
|
|||
|
|
To simplify setting a test coverage pattern, in GitLab 15.0 the
|
|||
|
|
[project setting for test coverage parsing](https://docs.gitlab.com/ee/ci/pipelines/settings.html#add-test-coverage-results-to-a-merge-request-deprecated)
|
|||
|
|
is being removed.
|
|||
|
|
|
|||
|
|
Instead, using the project’s `.gitlab-ci.yml`, provide a regular expression with the `coverage` keyword to set
|
|||
|
|
testing coverage results in merge requests.
|