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
fccdb622
Commit
fccdb622
authored
Aug 01, 2018
by
Daniel Gruesso
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update protected_environments.md
parent
56e7656e
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
doc/ci/environments/protected_environments.md
doc/ci/environments/protected_environments.md
+7
-7
No files found.
doc/ci/environments/protected_environments.md
View file @
fccdb622
...
...
@@ -9,13 +9,13 @@ while others are for production. As deploy jobs could be raised by different use
with different roles, it is very important that specific environments are "protected"
to avoid unauthorized people to affect them.
By default a protected environment does one simple thing:
E
nsures that only people
By default a protected environment does one simple thing:
it e
nsures that only people
with right privileges can deploy code to an environment, keeping it safe.
>**Note**:
A GitLab admin is always allowed to use environments, even if they are protected.
To protect
an environment, and to update
or unprotect an environment,
To protect
, update,
or unprotect an environment,
you need to have at least
[
Maintainer permission
][
perm
]
level.
## Configuring protected environments
...
...
@@ -27,19 +27,19 @@ you need to have at least [Maintainer permission][perm] level.
1.
From the 'Allowed to Deploy' dropdown menu, you can select the role and/or the users and/or the groups
you want to have deploy access. In the screenshot below, we chose the 'maintainers'. role
![Protected
e
nvironment form](img/protected_environments_form.png)
![Protected
E
nvironment form](img/protected_environments_form.png)
1.
Once done, the protected environment will appear in the "Protected
e
nvironments" list.
1.
Once done, the protected environment will appear in the "Protected
E
nvironments" list.
![Protected
e
nvironment list](img/protected_environments_list.png)
![Protected
E
nvironment list](img/protected_environments_list.png)
For the 'Allowed to Deploy' dropdown, there are some considerations to have in mind:
-
There are two roles to choose from:
-
*Maintainers*
- Will allow access to all maintainers in the project.
-
*Developers*
- Will allow access to all maintainers and all developers in the project.
-
You can only select groups that are associted with the project.
-
Only users that have at least Developer permimssion level will appear on 'Allowed to Deploy' dropdown menu.
-
You can only select groups that are associ
a
ted with the project.
-
Only users that have at least Developer permimssion level will appear on
the
'Allowed to Deploy' dropdown menu.
## Updating protected environments access
...
...
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