summaryrefslogtreecommitdiff
path: root/doc/ci
diff options
context:
space:
mode:
authorFabio Busatto <fabio@gitlab.com>2018-06-07 12:09:23 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2018-06-07 12:09:23 +0000
commit95dde46be57c8e1eacfa7fcd0bdfd299c635af6b (patch)
tree03728e8df6b4ab9a00cb1a7c2e1ae8020eb13637 /doc/ci
parent21469fa6b7364155c955fbef48880eb32419361d (diff)
downloadgitlab-ce-95dde46be57c8e1eacfa7fcd0bdfd299c635af6b.tar.gz
Resolve "Update docs to reflect the new place of the Kubernetes page"
Diffstat (limited to 'doc/ci')
-rw-r--r--doc/ci/environments.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/environments.md b/doc/ci/environments.md
index 36fd8affa5b..8ea2e0a81dc 100644
--- a/doc/ci/environments.md
+++ b/doc/ci/environments.md
@@ -114,7 +114,7 @@ Let's now see how that information is exposed within GitLab.
## Viewing the current status of an environment
-The environment list under your project's **Pipelines ➔ Environments**, is
+The environment list under your project's **Operations > Environments**, is
where you can find information of the last deployment status of an environment.
Here's how the Environments page looks so far.
@@ -167,7 +167,7 @@ that works.
You can't control everything, so sometimes things go wrong. When that unfortunate
time comes GitLab has you covered. Simply by clicking the **Rollback** button
that can be found in the deployments page
-(**Pipelines ➔ Environments ➔ `environment name`**) you can relaunch the
+(**Operations > Environments > `environment name`**) you can relaunch the
job with the commit associated with it.
>**Note:**