...
In addition to configuring Webhook to Jenkins at a Bitbucket repository level, you can also configure it at a project level, providing access to Webhook to Jenkins for all repositories in that project.
Before you begin, you must have at least one repository in the project that has Webhooks to Jenkins enabled and set to Inherited.
To confirm a repository has been set to Inherited, log in to Bitbucket as an Administrator, go to Repository Settings > Hooks > Webhook to Jenkins for Bitbucket and select Inherited (enabled) if not already set.
...
Git plugin version 4.11.4 or higher requires the notifyCommit token. See the Access token requirements for Git plugin 4.11.4+ article for instructions regarding generating and using the token.
| Info |
|---|
To determine which plugin your Jenkins instance currently uses, log into your Jenkins instance, and from the Dashboard, Click Manage Jenkins. Under System Configuration, select Manage Plugin and look for either the Git or Bitbucket Branch Source plugin. If neither plugin is shown, visit the Bitbucket Branch Source or Git plugin pages for information and download location, and consult your system administrator. If both plugins are present, examine the jobs you want to trigger and select the plugin that best matches your requirements.
See the What plugin should I use page for more information. |
...
Committers to Ignore - Select or enter the names of Bitbucket committers or access keys whose pushes/merges should NOT trigger a Jenkins notification.
Branch Options - Control the branches and tags allowed to build from. Refer to Trigger Jenkins for commits to a specific branch for details.
Limit Events - An event does not trigger a Jenkins build when that Limit Events option is removed. Refer to Limiting events which trigger Jenkins for details.
Trigger job poll if the branch is deleted - When a branch is merged or deleted in Bitbucket, select this option for Jenkins to remove the branch from its pipeline.
Trigger Pull request only if mergeable - Selecting this option only allows a build to trigger if the pull request is mergeable.
Job Parameters - Use this option to send custom URL parameters to Jenkins during the notification/trigger process. To use this option, you must also configure Jenkins to accept URL parameters. See Sending URL Parameters for details.
The Job Parameters feature is only available when using Git Plugin or Direct Job Trigger endpoints.
...