Skip to end of banner
Go to start of banner

Limiting events that trigger Jenkins

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Event filters

By default, Webhook To Jenkins for Bitbucket notifies Jenkins on git reference changes, pull requests creations, and reopenings. The Limit Events feature allows you to select which events can trigger Jenkins.

To limit which events trigger Jenkins:

  1. From your Bitbucket repository, click the Repository Settings icon > Hooks and select Enabled or click the Edit icon to change the previously enabled Webhook to Jenkins configuration.

  2. Click the Advanced Configuration tab and from the Limit Events options, select each event you want to enable. Each enabled event has a checkmark beside it.

Event

Description

Pull Request Opened

Triggers whenever a pull request is opened.

Pull Request Reopened

Triggers whenever a declined pull request is re-opened again.

Pull Request Approved

Triggers each time when reviewer(s) approves pull request and disabled by default.

Pull Request Merged

Triggers after a pull request is merged.

Open Pull Request Refs Changed

Triggers when a change occurs to any git reference, a base branch of at least one active Pull Request. This includes commits, pushes, edits, branch creations, and more.

All reference deleted events are filtered out. Does not trigger when refs are modified in the forked repository in the back-merge Pull Request.

Non-Pull Request Refs Changed

Similar to Open Pull Request Refs, but triggers for changes in references that do not participate in any active Pull Request.

Additional filters

FilterDescription
Trigger job if branch is deletedTrigger build on branch deletion. Can be useful for cleanup with multi-branch pipeline job.
Trigger Pull Request only if mergeableThis is an additional filter which can be used together with event filters.
When enabled, all configured Merge Checks will be respected (incl. 3rd-party ones), so that only mergeable PRs will be triggered when updated.
  • No labels