diff options
| author | Kamil Trzcinski <ayufan@ayufan.eu> | 2017-03-17 17:13:23 +0100 |
|---|---|---|
| committer | Kamil Trzcinski <ayufan@ayufan.eu> | 2017-03-17 17:16:56 +0100 |
| commit | 6cf8d34338f5d963a374abcc0e012800f8e316ac (patch) | |
| tree | b6b189a477f842eed935cca62fb0d2b188e0dbcb /doc/user | |
| parent | 7a623907528a77187e070c9721469df8bdd00ec8 (diff) | |
| download | gitlab-ce-6cf8d34338f5d963a374abcc0e012800f8e316ac.tar.gz | |
Update triggers documentation
Diffstat (limited to 'doc/user')
| -rw-r--r-- | doc/user/project/new_ci_build_permissions_model.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/user/project/new_ci_build_permissions_model.md b/doc/user/project/new_ci_build_permissions_model.md index b559d132590..55610a7b014 100644 --- a/doc/user/project/new_ci_build_permissions_model.md +++ b/doc/user/project/new_ci_build_permissions_model.md @@ -87,12 +87,12 @@ your Runners in the most possible secure way, by avoiding the following: By using an insecure GitLab Runner configuration, you allow the rogue developers to steal the tokens of other jobs. -## job triggers +## Pipeline triggers -[job triggers][triggers] do not support the new permission model. -They continue to use the old authentication mechanism where the CI job -can access only its own sources. We plan to remove that limitation in one of -the upcoming releases. +Since 9.0 [pipelnie triggers][triggers] do support the new permission model. +The new triggers do impersonate their associated user including their access +to projects and their project permissions. To migrate trigger to use new permisison +model use **Take ownership**. ## Before GitLab 8.12 |