Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
ef10f4c5
Commit
ef10f4c5
authored
May 25, 2017
by
Lin Jen-Shin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add docs for protected variables
parent
bd66bf08
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
21 additions
and
4 deletions
+21
-4
app/views/projects/variables/_content.html.haml
app/views/projects/variables/_content.html.haml
+1
-1
doc/ci/variables/README.md
doc/ci/variables/README.md
+20
-3
No files found.
app/views/projects/variables/_content.html.haml
View file @
ef10f4c5
%h4
.prepend-top-0
Secret
V
ariables
Secret
and protected v
ariables
%p
These variables will be set to environment by the runner.
%p
...
...
doc/ci/variables/README.md
View file @
ef10f4c5
...
...
@@ -11,6 +11,7 @@ this order:
1.
[
Trigger variables
][
triggers
]
(take precedence over all)
1.
[
Secret variables
](
#secret-variables
)
1.
[
Protected variables
](
#protected-variables
)
1.
YAML-defined
[
job-level variables
](
../yaml/README.md#job-variables
)
1.
YAML-defined
[
global variables
](
../yaml/README.md#variables
)
1.
[
Deployment variables
](
#deployment-variables
)
...
...
@@ -153,9 +154,26 @@ storing things like passwords, secret keys and credentials.
Secret variables can be added by going to your project's
**Settings ➔ Pipelines**
, then finding the section called
**Secret
V
ariables**
.
**Secret
and protected v
ariables**
.
Once you set them, they will be available for all subsequent jobs.
Once you set them, they will be available for all subsequent pipelines.
## Protected variables
>**Notes:**
-
This feature requires GitLab Runner 0.4.0 or higher.
-
A protected variable is a secret variable which is protected.
All secret variables could be protected. Whenever a secret variable is
protected, it would only be securely passed to pipelines running on the
protected branches or protected tags. The other pipelines would not get any
protected variables.
Protected variables can be added by going to your project's
**Settings ➔ Pipelines**
, then finding the section called
**Secret and protected variables**
, and check
*Protected*
.
Once you set them, they will be available for all subsequent pipelines.
## Deployment variables
...
...
@@ -381,7 +399,6 @@ export CI_REGISTRY_USER="gitlab-ci-token"
export
CI_REGISTRY_PASSWORD
=
"longalfanumstring"
```
[
ce-13784
]:
https://gitlab.com/gitlab-org/gitlab-ce/issues/13784
[
runner
]:
https://docs.gitlab.com/runner/
[
triggered
]:
../triggers/README.md
[
triggers
]:
../triggers/README.md#pass-job-variables-to-a-trigger
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment