File: pipeline_triggers.yml

package info (click to toggle)
libgitlab-api-v4-perl 0.27-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,500 kB
  • sloc: perl: 5,960; sh: 838; python: 63; makefile: 12
file content (29 lines) | stat: -rw-r--r-- 1,353 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
---
- triggers: triggers = GET projects/:project_id/triggers?
- trigger: trigger = GET projects/:project_id/triggers/:trigger_id
- create_trigger: trigger = POST projects/:project_id/triggers?
- edit_trigger: trigger = PUT projects/:project_id/triggers/:trigger_id?
- take_ownership_of_trigger: trigger = POST projects/:project_id/triggers/:trigger_id/take_ownership
- delete_trigger: DELETE projects/:project_id/triggers/:trigger_id
- method: trigger_pipeline
  spec: pipeline = POST projects/:project_id/trigger/pipeline?
  note: |
    The API authentication token (L</private_token> or L</access_token>
    parameters in a constructor) is not needed when using this method, however
    You must pass trigger token (generated at the trigger creation) as C<token>
    field and git ref name as C<ref> field in the C<%params> hash. You can also
    pass variables to be set in a pipeline in the C<variables> field. Example:

        my $pipeline = $api->trigger_pipeline(
            $project_id,
            {
                token => 'd69dba9162ab6ac72fa0993496286ada',
                'ref' => 'master',
                variables => {
                    variable1 => 'value1',
                    variable2 => 'value2',
                },
            },
        );

    Read more at L<https://docs.gitlab.com/ce/ci/triggers/#triggering-a-pipeline>.