Git Plugin 4.11.4+ requires the notifyCommit token when notifying Jenkins of any changes. Generate the token in Jenkins and enter it on the Bitbucket Cloud Webhook to Jenkins Settings page.
Attempting to use Webhook to Jenkins with Git plugin 4.11.4 or higher without adding the notifyCommit token to Bitbucket results in a Git Plugin 4.11.4+ requires access token for Jenkins notification message.
Generate a token in Jenkins
From your Jenkins instance, go to Manage Jenkins > Configure Global Security.
Find the Git plugin notifyCommit access tokens section.
Click Add new access token.
Enter the token name and click Generate.
Jenkins generates the
notifyCommittoken required in the Bitbucket Jenkins Base dialog.
Copy the token to your clipboard. The Access token is only displayed once.
Add the token to Webhook to Jenkins for Bitbucket Cloud
When adding a new Jenkins instance to your workspace in Bitbucket Cloud, the Add Jenkins Instance dialog contains the NotifyCommit Access Token field.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
You are currently in Webhook to Jenkins for Bitbucket Cloud documentation. Click Server/Data Center to move to that document. |
| Aura inline button | ||||
|---|---|---|---|---|
|
In this section
| Table of Contents | ||||
|---|---|---|---|---|
|
Related articles
Manage Webhook to Jenkins for Bitbucket Cloud
Configure Webhook to Jenkins for Bitbucket Cloud