jenkinsci / jenkinsci/scm-api-plugin
[JENKINS-56853] Pull Request validation by multiple jenkins - webhook name configuration
- Dominant language
- Java
- Stars
- 33
- Forks
- 87
- PR merge metrics
- No merged PRs in 30d
Description
I would like to have one PR validation per repo Webhook linked to a different Jenkins instance
The current behavior is as follows:
1.- Once Multibranch Pipeline is saved, scm api creates automatically the webhook for you... So under this repo Webhooks is set multiple webhooks per each of your masters (with their respective endpoints).
2.- Once a developer makes a new PR the build is launched in each of the masters... but just one validation (continuous-integration/jenkins/pr-merge) is happening for the repo. The last webhook which was joined to the repo.
---
Originally reported by
carlosrodlop, imported from: Pull Request validation by multiple jenkins - webhook name configuration
Raw content of original issue
I would like to have one PR validation per repo Webhook linked to a different Jenkins instance
The current behavior is as follows:
1.- Once Multibranch Pipeline is saved, scm api creates automatically the webhook for you... So under this repo Webhooks is set multiple webhooks per each of your masters (with their respective endpoints).
2.- Once a developer makes a new PR the build is launched in each of the masters... but just one validation (continuous-integration/jenkins/pr-merge) is happening for the repo. The last webhook which was joined to the repo.
2 attachments
- [pr-validation.png](https://issues.jenkins.io/secure/attachment/46610/pr-validation.png)
> 
- [webhooks.png](https://issues.jenkins.io/secure/attachment/46611/webhooks.png)
> 
Contributor guide
Research direction
Start by tracing how scm-api creates repository webhooks for Multibranch Pipeline jobs and how the PR validation name is assigned. Compare the current behavior described in the webhooks and PR-validation attachments; done means each webhook linked to a different Jenkins instance produces a distinct PR validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100