Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
33931327
Commit
33931327
authored
Jun 28, 2017
by
Sean
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README.md to reflect where "Secret variables" are located
parent
2b97d76d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/ci/ssh_keys/README.md
doc/ci/ssh_keys/README.md
+3
-3
No files found.
doc/ci/ssh_keys/README.md
View file @
33931327
...
...
@@ -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
c
ontent of your _private_ key that you c
reated 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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment