summaryrefslogtreecommitdiff
path: root/doc/ci
diff options
context:
space:
mode:
authorSean <sdm350@gmail.com>2017-06-28 22:47:52 +0000
committerSean <sdm350@gmail.com>2017-06-28 22:47:52 +0000
commit339313270a55cf1b4304aa6f017532d1544096a4 (patch)
treeab05211a87690d8e73cb09276b8161ac3b6e7986 /doc/ci
parent2b97d76d0b08a778710410df910a7601f6b8e9e7 (diff)
downloadgitlab-ce-339313270a55cf1b4304aa6f017532d1544096a4.tar.gz
Update README.md to reflect where "Secret variables" are located
Diffstat (limited to 'doc/ci')
-rw-r--r--doc/ci/ssh_keys/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/ssh_keys/README.md b/doc/ci/ssh_keys/README.md
index befaa06e918..cf25a8b618f 100644
--- a/doc/ci/ssh_keys/README.md
+++ b/doc/ci/ssh_keys/README.md
@@ -34,9 +34,9 @@ instructions to [generate an SSH key](../../ssh/README.md). Do not add a
passphrase to the SSH key, or the `before_script` will prompt for it.
Then, create a new **Secret Variable** in your project settings on GitLab
-following **Settings > Variables**. As **Key** add the name `SSH_PRIVATE_KEY`
-and in the **Value** field paste the content of your _private_ key that you
-created earlier.
+following **Settings > Pipelines** and look for the "Secret Variables" section.
+As **Key** add the name `SSH_PRIVATE_KEY` and in the **Value** field paste the
+content of your _private_ key that you created earlier.
It is also good practice to check the server's own public key to make sure you
are not being targeted by a man-in-the-middle attack. To do this, add another