summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoshua Lambert <joshua@gitlab.com>2018-02-20 15:52:36 -0500
committerJoshua Lambert <joshua@gitlab.com>2018-02-20 15:52:36 -0500
commit4503ad46d499ce4dd13ca95bbf23ac997b9c3be5 (patch)
tree16176d44c65a4d74b49f7ffd1580b2fe4d31bab4
parent54830fdcab2417b106825c5a5834c4f438d0b0ca (diff)
downloadgitlab-ce-update-browser-perf-testing-example-doc.tar.gz
-rw-r--r--doc/ci/examples/browser_performance.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/examples/browser_performance.md b/doc/ci/examples/browser_performance.md
index cd23b0ac1d7..42dc6ef36ba 100644
--- a/doc/ci/examples/browser_performance.md
+++ b/doc/ci/examples/browser_performance.md
@@ -27,7 +27,7 @@ Once you set up the Runner, add a new job to `.gitlab-ci.yml`, called `performan
This will create a `performance` job in your CI/CD pipeline and will run Sitespeed.io against the webpage you define. The GitLab plugin for Sitespeed.io is downloaded in order to export key metrics to JSON. The full HTML Sitespeed.io report will also be saved as an artifact, and if you have Pages enabled it can be viewed directly in your browser. For further customization options of Sitespeed.io, including the ability to provide a list of URLs to test, please consult their [documentation](https://www.sitespeed.io/documentation/sitespeed.io/configuration/).
For [GitLab Premium](https://about.gitlab.com/products/) users, key metrics are automatically
-extracted and shown right in the merge request widget. Learn more about [Browser Performance Testing](../../user/project/merge_requests/browser_performance_testing.md).
+extracted and shown right in the merge request widget. Learn more about [Browser Performance Testing](https://docs.gitlab.com/ee/user/project/merge_requests/browser_performance_testing.html).
## Performance testing on Review Apps