The SCM repository sends 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:
Create a service account: CloudBees CD/RO account to broker webhook interactions.
For each event trigger:
|Service accounts are for webhook triggers only. You must have access rights to create a service account. Contact your CloudBees CD/RO site administrator for assistance.|
Service accounts broker all webhook interactions between the GitHub and Bitbucket repositories and the CloudBees CD/RO webhook trigger. Access tokens are used by the service account to link webhook triggers to third-party systems.
Objects created when a service account runs a webhook trigger have the service account set as the object owner, and the owner name is
serviceAccount:<serviceAccountName>. Because the service account does not inherit privileges from the
Everyone group, all privileges for a service account must be specified explicitly. For example, to send email notifications when a pipeline has a service account as an owner, the service account must have the execute privilege configured for the related email configuration.
To create a service account:
From the CloudBees navigation, select CloudBees CD/RO.
From the CloudBees CD/RO main menu, navigate to. The Service Accounts dashboard displays.
Select Add service account. The New Service Account dialog displays.
Enter the service account Name and an optional Description. The best practice is to choose a name that represents the connection, such as GitHub. Select OK to save the new account.
Continue configuring service account settings. Refer to : Modifying service account attributes.
Select the three-dots menu to continue configuring the service account.
Modify service account name and description by selecting
Select DSL Export to download the service account in a DSL file.
Modify associated properties and property sheets by selecting Properties. For more information, refer to Configure properties or property sheets.
Configure authentication credentials by selecting Access tokens.
Specify explicit permissions for service account by selecting Access Control.
Remove the service account by selecting Delete.
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:
A user-defined name for this trigger object.
Name of project to be associated with the trigger object.
Details about the trigger object.
Select one of the following an object types: Release, Pipeline, Procedure, or Source code synchronization.
Select the name of the release, pipeline, procedure, or source code synchronization.
EC-Bitbucketcorresponding to the SCM tool you use for source control.
Use Secret token (GitHub triggers, only) A token which is used when creating the webhook in the source repository.
Use credential reference A unique Credential Project and Credential Name used when creating the webhook in the source repository.
A newline-separated list of repositories in the form
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.
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:
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:
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 Create a plugin 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 Create a repository webhook.
Select OK to finish.
Once you have set up the service account and configured a webhook trigger, you must create a repository webhook in the SCM.
You must configure the webhook in your source code repository and you must have write privileges for the repository. Before you start, ensure that you have the CloudBees CD/RO webhook endpoint that you created configuring a webhook trigger.
Once you have created a repository webhook, you must create a plugin configuration.
For more information, refer to: