jenkinsci / bitbucket-branch-source-plugin

Bitbucket Branch Source Plugin
https://plugins.jenkins.io/cloudbees-bitbucket-branch-source
MIT License
216 stars 352 forks source link

Web hooks checkbox described in documentation is no longer there #671

Open kwin opened 1 year ago

kwin commented 1 year ago

Describe your use-case which is not covered by existing documentation.

The checkbox with label "Auto-register webhook" described at https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/docs/USER_GUIDE.adoc#webhooks-registering for registering is no longer there with version 762.v969cfe087fc0

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

No response

Tyson1986 commented 1 year ago

Hi. I see the same behavior image

Expected is something like this image

KalleOlaviNiemitalo commented 1 year ago

AFAICT, the "Auto-register webhook" check box was removed in https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/53. The feature still exists but now you instead have to find the "Behaviours" section, click "Add" to open the dropdown menu, and choose "Override hook management" from the menu. This adds the "Override hook management" behaviour under the "General" heading. There, you can then choose either "Disable hook management" or "Use item credentials for hook management". If you don't add the "Override hook management" behaviour, then the default setting is controlled by the "Manage hooks" check box under "Bitbucket Endpoints" on the "Configure System" page.

Is someone willing to update the documentation?

Fragnite-hub commented 1 year ago

Hi There ! I would like to fix this issue #671 and #707 as well in the documentation. Could you quickly explain me how much should I write in the documentation as in how much of a description is required. Also i would like to add that this is going to be my first issue in the the world of open source so wish me luck :)

KalleOlaviNiemitalo commented 1 year ago

@Fragnite-hub, have you used the webhook registration feature so that you know how it works?