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.6, webhook triggers configured and scheduled before v10.1 no longer work. 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 GitHub or BitBucket 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 only.
-
Webhook triggers
The GitHub and Bitbucket repositories send a post
call to CloudBees CD/RO at a preconfigured endpoint, which processes the payload to run the target object.
In summary, here is what you need in order to trigger on webhooks:
-
One-time setup:
-
Create a service account: CloudBees CD/RO account to broker webhook interactions.
-
-
For each event trigger:
-
Configure a webhook trigger: In the CloudBees CD/RO server, configure the event trigger on the desired object.
-
Create a repository webhook: If not automatically configured when the trigger was created, explicitly configure the corresponding webhook in the GitHub or Bitbucket repository.
-
Creating a service account
Service accounts are for webhooks triggers only. |
A service account brokers all the webhook interactions between the GitHub repo and the pipeline webhook trigger. Its principal purpose is to hold the webhook session ID. A session associated with the service account is valid up to six months, by default, so it is a preferred way to manage a long-lasting webhook session.
You must have access rights to create a service account. Contact your CloudBees CD/RO site administrator for assistance. |
You can create a service account from CloudBees CD/RO.
-
From the CloudBees navigation, select CloudBees CD/RO.
-
From the CloudBees CD/RO main menu, navigate to
. The Service Accounts dashboard displays. -
Select New. The New Service Account dialog displays.
Figure 1. Create a new service account -
Enter the service account name in the Name field. The best practice is to choose a name that represents the connection, such as GitHub. Select OK to save the new account.
Configuring a webhook trigger
You can configure a webhook trigger from the Triggers page or at the time you run an object. Once the trigger is configured, it is armed and ready for the specified event.
To configure a webhook trigger:
-
Create the trigger. There are two options:
-
Option 1: From the CloudBees CD/RO main menu, select
. Select Add trigger at the top right of the screen. -
Option 2: Navigate to the object on which you want to set the trigger, select Run, and then select Triggers. The object’s trigger list displays. Select Add + to add a new trigger or select Edit to edit an existing trigger.
-
-
Enter the following information:
Field name
Description
Trigger Name
A user-defined name for this trigger object.
Plugin
Select
EC-GitHub
orEC-Bitbucket
corresponding to the SCM tool you use for source control.Trigger Type
Select Webhook.
Secret
(GitHub triggers, only) A secret you create, which is used when creating the webhook in the source repository.
Repositories
A newline-separated list of repositories in the form
organizationName/repositoryName
orusername/repositoryName
. Examples:myorg/testrepo
,myorg/testrepo1, `myorg/testrepo2
.Include Branches
A comma-separated list of branch names or patterns. Incoming events are discarded if they do not relate to one of the specified branches. Leave empty to process events for all branches except ones specified in the Exclude Branches parameter.
Exclude Branches
A comma-separated list of branch names or patterns. Incoming events are discarded when they relate to one of the specified branches. Leave empty to process events for all branches or the ones specified in the Include Branches parameter.
Process Push Events
Select this to run the trigger when the new commit appears in one of the monitored branches.
Process Pull Request Events
Select this to run the trigger when the pull request event occurs. Provide a list of comma-separated values. Run the trigger when one of the following actions has occurred:
opened
,edited
,closed_merged
,closed_discarded
,assigned
,unassigned
,review_requested
,review_request_removed
,ready_for_review
,labeled
,unlabeled
,synchronize
,locked
,unlocked
,reopened
.Process Commit Status Events
(GitHub triggers, only) Select this to run the trigger when the commit status has been changed in one of the specified branches. Provide a comma-separated list of status names from the following:
pending
,success
,failure
,error
.Run Schedule even if another instance is running
Select as appropriate for your needs.
Quiet Time Minutes
The number of minutes check-in-activity must be quiescent before launching the object.
-
Select Next. The Select Service Account dialog displays.
-
Select a previously-created service account.
-
Select Next. A summary of run-time details for the object displays.
-
Select OK. The Webhook Trigger Successfully Created dialog displays.
-
To create the webhook automatically in the repository, select Use the plugin procedure to automatically set up this webhook.
-
Select the configuration to use:
-
Use a pre-configured repository configuration from the Configuration dropdown list.
-
Create a new configuration. Refer to Creating a repository configuration.
-
Supply credentials manually.
-
-
Select whether to Bypass SSL Validation. If selected, the repository API does not check the SSL endpoint when sending an event payload.
-
-
If creating the repository webhook explicitly, note the secret URL on this page: you use it when you Creating a repository webhook.
-
Select OK to finish.
Creating a repository webhook
Once you have set up the service account and configured a webhook trigger, you must create a repository webhook in GitHub or Bitbucket.
Creating a repository webhook in GitHub
The steps in this section take place in your GitHub source code repository—you must have write privileges on the repository. Before starting, make sure you have the CloudBees CD/RO webhook endpoint and the webhook secret, both created in Configuring a webhook trigger.
-
Go to the settings page of your repository or organization.
-
Select Webhooks, then Add Webhook. The webhook configuration page displays.
Figure 2. GitHub webhook configuration -
Enter these values:
-
Payload URL: The webhook endpoint you generated when configuring a webhook trigger.
-
Content type: Select
application/json
. -
Secret: This is the secret used to validate the webhook payload from GitHub.
-
Choose Which events you would like to trigger this webhook?
-
-
Select Active and then select Add webhook.
-
Confirm the repository webhook is correctly configured.
GitHub sends an initial ping request to the registered payload URL. These are listed under Recent Deliveries.
Creating a repository webhook in Bitbucket
The steps in this section take place in your Bitbucket source code repository. You must have write privileges on the repository. Before starting, make sure you have the CloudBees CD/RO webhook endpoint that you created when configuring a webhook trigger above.
-
Go to the settings page of your repository.
-
Select Webhooks, then Add Webhook.
Figure 3. Bitbucket webhook configuration -
Enter these values:
-
Title: The title of this webhook.
-
Payload URL: The webhook endpoint you generated when configuring a webhook trigger above.
-
Status: Select Active.
-
Triggers: Select Push.
-
-
Select Save.
-
Confirm the repository webhook is correctly configured.
GitHub sends an initial ping request to the registered payload URL. These are listed under Recent Deliveries.
Creating a repository configuration
-
For GitHub configurations, refer to GitHub—plugin configurations.
-
For Bitbucket configurations, refer to Bitbucket—plugin configurations.
Polling triggers
Configure CloudBees CD/RO to poll the specified Git source control repository for updates at a preconfigured schedule. If an update is detected, the runtime object is run. Once the trigger is configured, it is armed and ready to poll for the specified event.
Polling triggers are supported for Git only. |
Configuring a polling trigger
You can configure a polling trigger from the Triggers page or at the time you run an object. Once the trigger is configured, it is armed and ready to poll for the specified event.
To configure a polling trigger:
-
Create the trigger. There are two options:
-
Option 1: From the CloudBees CD/RO main menu, select
. Select Add trigger at the top right of the screen. -
Option 2: Navigate to the object on which you want to set the trigger, select Run, and then select Triggers. The object’s trigger list displays. Select Add + to add a new trigger or select Edit to edit an existing trigger.
-
-
Enter the following information:
Field name
Description
Trigger Name
User-defined name for this trigger object.
Plugin
Select
EC-Git
.Trigger Type
Select Polling.
Configuration Name
(required)
-
Use a pre-configured repository configuration from the Configuration Name dropdown list.
-
Create a new configuration. Refer to Creating a repository configuration.
Git repository URL
(required) A repository URL, for example,
git://server/repo.git
,https://github.com/github/testrepo.git
.Monitor
Specifies what to monitor:
Branch
orTags
Git branch name
The name of the Git branch to watch for changes, for example,
main
,dev
.Run Schedule even if another instance is running
Quiet Time Minutes
The number of minutes no check-in-activity is required before launching the procedure.
-
-
Select Next. A summary of run-time details for the object displays.
-
Select OK.
API access
These API resources are available to programmatically create and manage event-based triggers:
-
To create and manage webhook service accounts, refer to Service accounts for webhooks.
-
To create and manage triggers, refer to Trigger.