Commit dccf910a authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch 'selhorn-nav-update-6' into 'master'

Updated nav to match standards

See merge request gitlab-org/gitlab!67788
parents 62ba3b1c 44339a64
...@@ -115,11 +115,15 @@ We also use two secure variables: ...@@ -115,11 +115,15 @@ We also use two secure variables:
## Storing API keys ## Storing API keys
To add secure variables, navigate to your project's To store API keys as secure variables:
**Settings > CI/CD > Variables**. The variables defined
in the project settings are sent along with the build script to the runner. 1. On the top bar, select **Menu > Projects** and find your project.
1. On the left sidebar, select **Settings > CI/CD**.
1. Expand **Variables**.
The variables 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 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 your project's `.gitlab-ci.yml` file. It is also important that the secret's value
is hidden in the job log. is hidden in the job log.
You access added variable by prefixing it's name with `$` (on non-Windows runners) You access added variable by prefixing it's name with `$` (on non-Windows runners)
...@@ -128,4 +132,4 @@ or `%` (for Windows Batch runners): ...@@ -128,4 +132,4 @@ or `%` (for Windows Batch runners):
- `$VARIABLE`: Use for non-Windows runners - `$VARIABLE`: Use for non-Windows runners
- `%VARIABLE%`: Use for Windows Batch runners - `%VARIABLE%`: Use for Windows Batch runners
Read more about the [CI/CD variables](../../variables/index.md). Read more about [CI/CD variables](../../variables/index.md).
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