Commit 25f970cf authored by Marcel Amirault's avatar Marcel Amirault

Update details about SSH keys in ci jobs

parent 775bb585
...@@ -36,7 +36,8 @@ with any type of [executor](https://docs.gitlab.com/runner/executors/) ...@@ -36,7 +36,8 @@ with any type of [executor](https://docs.gitlab.com/runner/executors/)
`~/.ssh/authorized_keys`) or add it as a [deploy key](../../user/project/deploy_keys/index.md) `~/.ssh/authorized_keys`) or add it as a [deploy key](../../user/project/deploy_keys/index.md)
if you are accessing a private GitLab repository. if you are accessing a private GitLab repository.
The private key is displayed in the job log, unless you enable In the following example, the `ssh-add -` command does not display the value of
`$SSH_PRIVATE_KEY` in the job log, though it could be exposed if you enable
[debug logging](../variables/README.md#debug-logging). You might also want to [debug logging](../variables/README.md#debug-logging). You might also want to
check the [visibility of your pipelines](../pipelines/settings.md#visibility-of-pipelines). check the [visibility of your pipelines](../pipelines/settings.md#visibility-of-pipelines).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment