[JENKINS-57860] Optionally allow for idempotent handling of SCMEvents

Related to: https://issues.jenkins-ci.org/browse/JENKINS-57014

GitHub Conversation: https://github.com/jenkinsci/github-branch-source-plugin/pull/216

When GitHub publishes an event for a Deployment, the revision in the event payload is the same as the revision in the push event payload. Thus, the below line of code will not execute a pipeline upon receiving the deployment webhook. We would like the ability to optionally toggle on/off handling SCMEvents in an idempotent manner.

https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.java#L1546

---
Originally reported by philmadden, imported from: Optionally allow for idempotent handling of SCMEvents

• assignee: philmadden
  
• status: Open
  
• priority: Minor
  
• component(s): branch-api-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251211-141027
  

Raw content of original issue

Related to: https://issues.jenkins-ci.org/browse/JENKINS-57014

GitHub Conversation: https://github.com/jenkinsci/github-branch-source-plugin/pull/216


When GitHub publishes an event for a Deployment, the revision in the event payload is the same as the revision in the push event payload. Thus, the below line of code will not execute a pipeline upon receiving the deployment webhook. We would like the ability to optionally toggle on/off handling SCMEvents in an idempotent manner.


https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.java#L1546

Start at src/main/java/jenkins/branch/MultiBranchProject.java around line 1546, then review the related JENKINS-57014 issue and the GitHub conversation in pull request #216. Determine how an optional idempotent SCMEvent-handling mode should be exposed and verify that deployment events with the same revision as push events are handled as requested.

Written by the indexing model from the issue text.