Skip to main content

Configure triggers

An Auto Trigger starts your Pipeline automatically when a GitLab event happens, instead of you clicking Run Pipeline every time — configuration lives inside the Pipeline Source settings, not a separate step. This tutorial configures a Trigger, then shows how to manage it afterward.

Prerequisites​

  • You have an account on the FPT Cloud DevOps Platform.
  • At least one Pipeline has been created and saved. See Create and configure a pipeline.
  • A GitLab Connection is configured.
  • You have administrator access to the repository on GitLab.
warning

Auto Trigger currently supports GitLab only. GitHub and Bitbucket support is coming soon.

Enable Auto Trigger​

Update Pipeline Source with trigger enabled

  1. While configuring the Pipeline, open the Pipeline Source card, or click the Edit icon on the Triggers step summary.
  2. In Update Pipeline Source, confirm the Git account connection uses a GitLab repository.
  3. Turn on Enable code source trigger(s).

The toggle stays disabled with a "coming soon" note when the connected repository is GitHub or Bitbucket. Once enabled, the event and branch filter options appear in the same panel.

Select event types​

You must select at least one event type under Enable triggers for. See Triggers reference for the full table.

The Pipeline runs whenever the selected event occurs — for example, a Push for continuous integration, or a Tag push for a release Pipeline.

Configure a Branch Filter​

After you select an event type, choose how the Trigger applies to branches under Applied to branches:

  • All branches — the default. Every branch matching the selected events triggers the Pipeline.

  • Filtered branches by name — add branch names under Name included and Name excluded (press Enter after each name). Leave Name included empty to match all branches except those under Name excluded.

    Filtered branches by name

  • Filtered branches by regex — enter a pattern in Source Branch Regex and, if needed, Target Branch Regex. See Triggers reference for pattern examples.

    Filtered branches by regex

Only one option applies at a time — switching to a different one replaces the current filter.

tip

The regex fields don't validate the pattern as you type. Double-check the syntax before saving.

Register the Webhook in GitLab​

Webhook url token

The system generates a Webhook URL and Token automatically in the same panel — you cannot edit these directly.

  1. Copy the Webhook URL.
  2. Copy the Token.
  3. Open the GitLab repository, then go to Settings → Webhooks.
  4. Create a new Webhook and paste the URL and Token.
  5. Select the relevant events.
  6. Click Add Webhook.

GitLab can now send events to FPT Cloud DevOps Platform, and the Pipeline triggers automatically on a matching event.

Manage an existing Trigger​

Triggers step summary

The Triggers step shows a read-only summary of the current configuration — whether Auto Trigger is enabled, plus a shortcut to change it.

Edit a Trigger​

Update Pipeline Source panel opened from the Triggers step

  1. On the Triggers step, click the Edit icon to reopen the same Update Pipeline Source panel used for initial configuration.
  2. Update the event types, branch filter, or toggle.
  3. Click Save, then Save Pipeline.

Regenerate the Token​

  1. Open Update Pipeline Source via the Edit icon on the Triggers step.
  2. Click Regenerate token next to the Secret token field, then confirm if prompted.
warning

The old Token is invalidated immediately. Update the new Token in the GitLab Webhook right away, or the Webhook stops working.

Next steps​