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
0
Merge Requests
0
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
Tatuya Kamada
gitlab-ce
Commits
40e3a701
Commit
40e3a701
authored
Mar 27, 2017
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'triggers-docs' into 'master'
Triggers docs See merge request !10050
parents
7181b345
6cf8d343
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
26 additions
and
8 deletions
+26
-8
doc/ci/triggers/README.md
doc/ci/triggers/README.md
+21
-3
doc/ci/triggers/img/triggers_page.png
doc/ci/triggers/img/triggers_page.png
+0
-0
doc/user/project/new_ci_build_permissions_model.md
doc/user/project/new_ci_build_permissions_model.md
+5
-5
No files found.
doc/ci/triggers/README.md
View file @
40e3a701
...
...
@@ -4,6 +4,7 @@
-
[
Introduced
][
ci-229
]
in GitLab CE 7.14.
-
GitLab 8.12 has a completely redesigned job permissions system. Read all
about the
[
new model and its implications
](
../../user/project/new_ci_build_permissions_model.md#job-triggers
)
.
-
GitLab 9.0 introduced a trigger ownership to solve permission problems.
Triggers can be used to force a rebuild of a specific
`ref`
(branch or tag)
with an API call.
...
...
@@ -21,13 +22,30 @@ overview of the time the triggers were last used.
![
Triggers page overview
](
img/triggers_page.png
)
## Take ownership
Each created trigger when run will impersonate their associated user including
their access to projects and their project permissions.
You can take ownership of existing triggers by clicking
*Take ownership*
.
From now on the trigger will be run as you.
## Legacy triggers
Old triggers, created before 9.0 will be marked as Legacy. Triggers with
the legacy label do not have an associated user and only have access
to the current project.
Legacy trigger are considered deprecated and will be removed
with one of the future versions of GitLab.
## Revoke a trigger
You can revoke a trigger any time by going at your project's
**Settings > Triggers**
and hitting the
**Revoke**
button. The action is
irreversible.
## Trigger a
job
## Trigger a
pipeline
> **Note**:
Valid refs are only the branches and tags. If you pass a commit SHA as a ref,
...
...
@@ -63,7 +81,7 @@ below.
See the
[
Examples
](
#examples
)
section for more details on how to actually
trigger a rebuild.
## Trigger a
job
from webhook
## Trigger a
pipeline
from webhook
> Introduced in GitLab 8.14.
...
...
@@ -117,7 +135,7 @@ curl --request POST \
"https://gitlab.example.com/api/v4/projects/9/trigger/pipeline?token=TOKEN&ref=master"
```
### Triggering a
job
within `.gitlab-ci.yml`
### Triggering a
pipeline
within `.gitlab-ci.yml`
You can also benefit by using triggers in your
`.gitlab-ci.yml`
. Let's say that
you have two projects, A and B, and you want to trigger a rebuild on the
`master`
...
...
doc/ci/triggers/img/triggers_page.png
View replaced file @
7181b345
View file @
40e3a701
5 KB
|
W:
|
H:
108 KB
|
W:
|
H:
2-up
Swipe
Onion skin
doc/user/project/new_ci_build_permissions_model.md
View file @
40e3a701
...
...
@@ -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.
The
y 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
...
...
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