root
/
gitlab-ce
mirror of https://gitlab.com/free-releases/gitlab-ce.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Merge branch 'docs/60785-docs-feedback-masked-variables-is-not-clear-what-unescaped-characters-means' into 'master' 

Clarify masked variables docs

Closes #60785

See merge request gitlab-org/gitlab-ce!27580
This commit is contained in:
Evan Read 2019-04-28 22:55:05 +00:00
parent 6246979a86 7bb8286562
commit 05cad997cd
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/ci/variables/README.md
View File

@ -143,14 +143,16 @@ This means that the value of the variable will be hidden in job logs,
though it must match certain requirements to do so: though it must match certain requirements to do so:
- The value must be in a single line. - The value must be in a single line.
- The value must not have escape characters. - The value must contain only letters, numbers, or underscores.
- The value must not have escape characters, such as `\"`
- The value must not use variables. - The value must not use variables.
- The value must not have any whitespace. - The value must not have any whitespace.
- The value must be at least 8 characters long. - The value must be at least 8 characters long.
If the value does not meet the requirements above, then the CI variable will fail to save. The above rules are validated using the regex `/\A\w{8,}\z/`. If the value
In order to save, either alter the value to meet the masking requirements does not meet the requirements above, then the CI variable will fail to save.
or disable `Masked` for the variable. In order to save, either alter the value to meet the masking requirements or
disable `Masked` for the variable.
### Syntax of environment variables in job scripts ### Syntax of environment variables in job scripts