summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMoetaz <moetez.93@gmail.com>2018-03-29 10:47:52 +0000
committerMoetaz <moetez.93@gmail.com>2018-03-29 10:47:52 +0000
commit2f140cfad4adc349677644520e245a359cafbfbb (patch)
treef65166a78b4470b53a27a4e3fb2b9b505b5838c3
parentf39beff64cafba35097637e5e9c3a5f999745eaa (diff)
downloadgitlab-ce-2f140cfad4adc349677644520e245a359cafbfbb.tar.gz
Update README.md (settings -> pipelines is renamed to settings -> CI / CD )
-rw-r--r--doc/ci/examples/deployment/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/examples/deployment/README.md b/doc/ci/examples/deployment/README.md
index e80e246c5dd..2dcdc2d41ec 100644
--- a/doc/ci/examples/deployment/README.md
+++ b/doc/ci/examples/deployment/README.md
@@ -111,7 +111,7 @@ We also use two secure variables:
## Storing API keys
Secure Variables can added by going to your project's
-**Settings ➔ Pipelines ➔ Secret variables**. The variables that are defined
+**Settings ➔ CI / CD ➔ Secret variables**. The variables that are defined
in the project settings are sent along with the build script to the Runner.
The secure variables are stored out of the repository. Never store secrets in
your project's `.gitlab-ci.yml`. It is also important that the secret's value