Adding a project for a Bitbucket repository will not trigger any prebuilds or add any webhooks

[gtsiolis]

Problem to solve

Back in #7251, we've added support for Bitbucket projects.

However, when adding a project for a Bitbucket repository will not trigger any prebuilds or add any webhooks. See relevant comment in #7251 (comment):

... in contrast with GitLab and GitHub repositories, adding a Bitbucket repository 🅰️ does not add a webhook for enabling prebuilds and 🅱️ does not automatically trigger a first prebuilds after adding the project.

Proposal

Let's 🅰️ add a webhook when adding a Bitbucket repository and 🅱️ trigger a prebuild when adding the project to follow the behavior of the product when adding GitLab and GitHub repositories as projects.

Cc @AlexTugarev in case adding the webhook is not the best way forward here.

[jldec]

Thanks for opening this followup issue @gtsiolis
We should (within reason) try to offer a consistent UX for projects across git providers.
/schedule

[roboquat]

@jldec: Issue scheduled in the meta team (WIP: 0)

In response to this:

Thanks for opening this followup issue @gtsiolis
We should (within reason) try to offer a consistent UX for projects across git providers.
/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jldec]

The fix for this issue should result in the equivalent of enabling prebuilds with a prefixed /#prebuild URL.

Users should not have to use the manually prefixed URL for prebuilds. This is important because (from #6688 (comment))

Also, the manual prefix implementation is no longer correct (it doesn't associate Projects to prebuilds, doesn't use Incremental Prebuilds if enabled, etc).

cc: @gtsiolis @AlexTugarev

[AlexTugarev]

@jldec and @gtsiolis, just to clarify what enablement of prebulids means as it is implemented currently: two things needs to be true in order for a prebuild to start on a new commit. first the app/webhook needs to be installed to get the push event into Gitpod, and then the event handler needs to find/evaluate a Gitpod config for this repo to decide if a prebuild should be started.

PR #7422 targets only the creation of a missing webhook. if the config+tasks do not exist in the repo, prebuilds won't be triggered automatically.

[jldec]

PR #7422 targets only the creation of a missing webhook. if the config+tasks do not exist in the repo, prebuilds won't be triggered automatically.

That matches my expectations @AlexTugarev
I was just a bit confused by comments in the PR and in #7424. - sorry about that