summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-08-19 13:56:17 +1000
committerEvan Read <eread@gitlab.com>2019-08-19 13:56:17 +1000
commit1efa52be1aa60c25fe29b45a25b78b4c8c7f69b1 (patch)
treebbfc3efc99bb557f35343286d642d14d49ed25e9
parent0586d420ea31d3bd28c5788f0a0a339e91c889ab (diff)
downloadgitlab-ce-docs/clarify-new-values.tar.gz
Clarify when new values are validdocs/clarify-new-values
-rw-r--r--doc/ci/variables/README.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/ci/variables/README.md b/doc/ci/variables/README.md
index d741482b662..5a15b907da0 100644
--- a/doc/ci/variables/README.md
+++ b/doc/ci/variables/README.md
@@ -94,7 +94,10 @@ This means that the value of the variable will be hidden in job logs,
though it must match certain requirements to do so:
- The value must be in a single line.
-- The value must only consist of characters from the Base64 alphabet ([RFC4648](https://tools.ietf.org/html/rfc4648)) with the addition of `@` and `:`.
+- The value must only consist of characters from the Base64 alphabet (RFC4648).
+
+ [In GitLab 12.2](https://gitlab.com/gitlab-org/gitlab-ce/issues/63043)
+ and newer, `@` and `:` are also valid values.
- The value must be at least 8 characters long.
- The value must not use variables.
@@ -509,7 +512,7 @@ Below you can find supported syntax reference:
1. Checking for an empty variable
Examples:
-
+
- `$VARIABLE == ""`
- `$VARIABLE != ""` (introduced in GitLab 11.11)