diff options
author | Olivier Gonzalez <ogonzalez@gitlab.com> | 2018-11-13 12:25:50 +0100 |
---|---|---|
committer | Olivier Gonzalez <ogonzalez@gitlab.com> | 2018-11-13 12:25:50 +0100 |
commit | 4169531f88725eab6f988a18d45a123e61c1ad33 (patch) | |
tree | d98e578b7502a83e792dfe03c84304967ebff513 | |
parent | 9656b423ddb60e9f775975a32e3832877d2cf0ea (diff) | |
download | gitlab-ce-docs-document_new_reports_syntax-ce.tar.gz |
Capitalize report namedocs-document_new_reports_syntax-ce
-rw-r--r-- | doc/ci/examples/browser_performance.md | 2 | ||||
-rw-r--r-- | doc/ci/examples/code_quality.md | 2 | ||||
-rw-r--r-- | doc/ci/examples/container_scanning.md | 2 | ||||
-rw-r--r-- | doc/ci/examples/dast.md | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/ci/examples/browser_performance.md b/doc/ci/examples/browser_performance.md index 60c7ef76106..7c3b3a65675 100644 --- a/doc/ci/examples/browser_performance.md +++ b/doc/ci/examples/browser_performance.md @@ -41,7 +41,7 @@ The above example will create a `performance` job in your CI/CD pipeline and wil Sitespeed.io against the webpage you defined in `URL` to gather key metrics. The [GitLab plugin](https://gitlab.com/gitlab-org/gl-performance) for Sitespeed.io is downloaded in order to save the report as a -[performance report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportsperformance) +[Performance report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportsperformance) that you can later download and analyze. Due to implementation limitations we always take the latest Performance artifact available. diff --git a/doc/ci/examples/code_quality.md b/doc/ci/examples/code_quality.md index f8597cafefc..ae000b9d30d 100644 --- a/doc/ci/examples/code_quality.md +++ b/doc/ci/examples/code_quality.md @@ -36,7 +36,7 @@ code_quality: The above example will create a `code_quality` job in your CI/CD pipeline which will scan your source code for code quality issues. The report will be saved as a -[codequality report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportscodequality) +[Code Quality report artifact](../../ci/yaml/README.md#artifactsreportscodequality) that you can later download and analyze. Due to implementation limitations we always take the latest Code Quality artifact available. diff --git a/doc/ci/examples/container_scanning.md b/doc/ci/examples/container_scanning.md index 35bf7e45c01..68330261910 100644 --- a/doc/ci/examples/container_scanning.md +++ b/doc/ci/examples/container_scanning.md @@ -51,7 +51,7 @@ The above example will create a `container_scanning` job in your CI/CD pipeline, the image from the [Container Registry](../../user/project/container_registry.md) (whose name is defined from the two `CI_APPLICATION_` variables) and scan it for possible vulnerabilities. The report will be saved as a -[container scanning report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportscontainer_scanning) +[Container Scanning report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportscontainer_scanning) that you can later download and analyze. Due to implementation limitations we always take the latest Container Scanning artifact available. diff --git a/doc/ci/examples/dast.md b/doc/ci/examples/dast.md index 706923376f5..0ca89eb6700 100644 --- a/doc/ci/examples/dast.md +++ b/doc/ci/examples/dast.md @@ -40,7 +40,7 @@ dast: The above example will create a `dast` job in your CI/CD pipeline which will run the tests on the URL defined in the `website` variable (change it to use your own) and scan it for possible vulnerabilities. The report will be saved as a -[dast report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportsdast) +[DAST report artifact](https://docs.gitlab.com/ee//ci/yaml/README.html#artifactsreportsdast) that you can later download and analyze. Due to implementation limitations we always take the latest DAST artifact available. |