diff options
Diffstat (limited to 'doc/ci/yaml/artifacts_reports.md')
| -rw-r--r-- | doc/ci/yaml/artifacts_reports.md | 51 |
1 files changed, 12 insertions, 39 deletions
diff --git a/doc/ci/yaml/artifacts_reports.md b/doc/ci/yaml/artifacts_reports.md index e931a8b3b4e..5867a5b3506 100644 --- a/doc/ci/yaml/artifacts_reports.md +++ b/doc/ci/yaml/artifacts_reports.md @@ -1,7 +1,7 @@ --- stage: Verify group: Pipeline Execution -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments +info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments --- # GitLab CI/CD artifacts reports types **(FREE ALL)** @@ -17,7 +17,8 @@ Use [`artifacts:reports`](index.md#artifactsreports) to: Artifacts created for `artifacts: reports` are always uploaded, regardless of the job results (success or failure). You can use [`artifacts:expire_in`](index.md#artifactsexpire_in) to set an expiration -date for the artifacts. +time for the artifacts, which overrides the instance's [default setting](../../administration/settings/continuous_integration.md#maximum-artifacts-size). +GitLab.com might have a [different default artifacts expiry value](../../user/gitlab_com/index.md#gitlab-cicd). Some `artifacts:reports` types can be generated by multiple jobs in the same pipeline, and used by merge request or pipeline features from each job. @@ -30,8 +31,6 @@ not supported. Track progress on adding support in [this issue](https://gitlab.c ## `artifacts:reports:accessibility` -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/39425) in GitLab 12.8. - The `accessibility` report uses [pa11y](https://pa11y.org/) to report on the accessibility impact of changes introduced in merge requests. @@ -91,9 +90,6 @@ The following is an example of what a job annotations report might look like: ## `artifacts:reports:api_fuzzing` **(ULTIMATE ALL)** -> - Introduced in GitLab 13.4. -> - Requires GitLab Runner 13.4 or later. - The `api_fuzzing` report collects [API Fuzzing bugs](../../user/application_security/api_fuzzing/index.md) as artifacts. @@ -143,8 +139,7 @@ GitLab can display the results of coverage report in the merge request ## `artifacts:reports:codequality` -> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/212499) to GitLab Free in 13.2. -> - Support for multiple reports in diff annotations and full pipeline report [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9014) in 15.7. +> Support for multiple reports in diff annotations and full pipeline report [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9014) in 15.7. The `codequality` report collects [code quality issues](../testing/code_quality.md). The collected code quality report uploads to GitLab as an artifact. @@ -155,6 +150,8 @@ GitLab can display the results of one or more reports in: - The merge request [diff annotations](../testing/code_quality.md#merge-request-changes-view). - The [full report](../testing/metrics_reports.md). +The [`artifacts:expire_in`](../yaml/index.md#artifactsexpire_in) value is set to `1 week`. + ## `artifacts:reports:container_scanning` **(ULTIMATE ALL)** The `container_scanning` report collects [Container Scanning vulnerabilities](../../user/application_security/container_scanning/index.md). @@ -169,9 +166,6 @@ GitLab can display the results of one or more reports in: ## `artifacts:reports:coverage_fuzzing` **(ULTIMATE ALL)** -> - Introduced in GitLab 13.4. -> - Requires GitLab Runner 13.4 or later. - The `coverage_fuzzing` report collects [coverage fuzzing bugs](../../user/application_security/coverage_fuzzing/index.md). The collected coverage fuzzing report uploads to GitLab as an artifact. GitLab can display the results of one or more reports in: @@ -233,8 +227,6 @@ GitLab can display the results of one or more reports in: ## `artifacts:reports:dotenv` -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/17066) in GitLab 12.9. - The `dotenv` report collects a set of environment variables as artifacts. The collected variables are registered as runtime-created variables of the job, @@ -294,24 +286,8 @@ concatenate them into a single file. Use either: - A combination of both (`junit: [rspec.xml, test-results/TEST-*.xml]`). - Directories are not supported(`junit: test-results`, `junit: test-results/**`). -<!--- start_remove The following content will be removed on remove_date: '2023-11-22' --> - -## `artifacts:reports:license_scanning` **(ULTIMATE ALL)** - -> Introduced in GitLab 12.8. - -The license scanning report was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387561) -in GitLab 15.9 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/421363) in GitLab 16.3. -You should instead migrate to use [License approval policies](../../user/compliance/license_approval_policies.md) and -the [new method of license scanning](../../user/compliance/license_scanning_of_cyclonedx_files/index.md). - -<!--- end_remove --> - ## `artifacts:reports:load_performance` **(PREMIUM ALL)** -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35260) in GitLab 13.2. -> - Requires GitLab Runner 11.5 and above. - The `load_performance` report collects [Load Performance Testing metrics](../testing/load_performance_testing.md). The report is uploaded to GitLab as an artifact. @@ -330,14 +306,18 @@ GitLab can display the results of one or more reports in the merge request ## `artifacts:reports:requirements` **(ULTIMATE ALL)** -> [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2859) in GitLab 13.1. - The `requirements` report collects `requirements.json` files. The collected Requirements report uploads to GitLab as an artifact and existing [requirements](../../user/project/requirements/index.md) are marked as Satisfied. GitLab can display the results of one or more reports in the [project requirements](../../user/project/requirements/index.md#view-a-requirement). +## `artifacts:reports:repository_xray` **(ULTIMATE ALL)** + +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/432235) in GitLab 16.7. + +The `repository_xray` report collects information about your repository for use by AI in code suggestions. + ## `artifacts:reports:sast` > [Moved](https://gitlab.com/groups/gitlab-org/-/epics/2098) from GitLab Ultimate to GitLab Free in 13.3. @@ -352,10 +332,6 @@ GitLab can display the results of one or more reports in: ## `artifacts:reports:secret_detection` -> - Introduced in GitLab 13.1. -> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/222788) to GitLab Free in 13.3. -> - Requires GitLab Runner 11.5 and above. - The `secret-detection` report collects [detected secrets](../../user/application_security/secret_detection/index.md). The collected Secret Detection report is uploaded to GitLab. @@ -367,9 +343,6 @@ GitLab can display the results of one or more reports in: ## `artifacts:reports:terraform` -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/207528) in GitLab 13.0. -> - Requires [GitLab Runner](https://docs.gitlab.com/runner/) 11.5 and above. - The `terraform` report obtains a Terraform `tfplan.json` file. [JQ processing required to remove credentials](../../user/infrastructure/iac/mr_integration.md#configure-terraform-report-artifacts). The collected Terraform plan report uploads to GitLab as an artifact. |