summaryrefslogtreecommitdiff
path: root/doc/ci
diff options
context:
space:
mode:
authorKamil Trzcinski <ayufan@ayufan.eu>2016-02-09 01:08:49 +0100
committerKamil Trzcinski <ayufan@ayufan.eu>2016-02-09 01:08:49 +0100
commit078ec5e414bde2d8014d40cd476917d75d4756ac (patch)
treeed646f38d9fabcd586654cd66c7b0f07456759f8 /doc/ci
parent4558bb1f4a4be88bd05f0de9826686a86d63acad (diff)
downloadgitlab-ce-078ec5e414bde2d8014d40cd476917d75d4756ac.tar.gz
Add information about expose of build variables.variables-build-log
Diffstat (limited to 'doc/ci')
-rw-r--r--doc/ci/variables/README.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/ci/variables/README.md b/doc/ci/variables/README.md
index 862cacda586..018d1898594 100644
--- a/doc/ci/variables/README.md
+++ b/doc/ci/variables/README.md
@@ -77,9 +77,12 @@ More information about Docker integration can be found in [Using Docker Images](
GitLab CI allows you to define per-project **Secure Variables** that are set in build environment.
The secure variables are stored out of the repository (the `.gitlab-ci.yml`).
-These variables are securely stored in GitLab CI database and are hidden in the build log.
+The variables are securely passed to GitLab Runner and are available in build environment.
It's desired method to use them for storing passwords, secret keys or whatever you want.
+**The value of the variable can be shown in build log if explicitly asked to do so.**
+If your project is public or internal you can make the builds private.
+
Secure Variables can added by going to `Project > Variables > Add Variable`.
They will be available for all subsequent builds.