Event-based triggers support continuous integration (CI) models by automatically running pipelines, procedures, and releases based on external events. Trigger support in CloudBees CD/RO allows you to integrate with external tools such as source control management (SCM) systems. For example, you can configure a Git repository to automatically trigger a release upon code check-in.
Once configured, you can view all triggers in the system on the Triggers page. From the CloudBees CD/RO main menu, select .
To locate a trigger in the list, you can use the search field or filter by project, object, or tag.
| As of v10.8, webhook triggers configured and scheduled before v10.1 have been deleted. Polling triggers configured and scheduled prior to v10.1 continue to work, but they are not available from the UI to review or run. |
CloudBees CD/RO supports these event-based triggers:
-
Webhook triggers: An inbound, asynchronous event that triggers an action. Webhook triggers support these actions:
-
Pipeline run
-
Release run
-
Procedure run
-
Source code synchronization run
A service account is required for webhook triggers.
-
-
Polling triggers: An internal trigger is periodically sent to an external Git repository to determine if an event such as a code check-in has happened. And, if so, an action is initiated. Polling triggers support these actions:
-
Pipeline run
-
Release run
-
Procedure run
-
Source code synchronization run
Polling triggers are supported for Git repositories and properties only.
-