[JENKINS-41074] UX Issue with Polling in Multibranch Pipeline

There is general confusing about how polling behaves in multibranch pipeline. Polling will continue to trigger the same revision over and over again because mutlibranch is pinned to the revision found in computation.

For now we should disable the trigger in properties step of a multibranch pipeline.

The recommendation for users not using webhooks would be to configure the "Periodically if not otherwise run" but this will add more api calls.

---
Originally reported by hrmpw, imported from: UX Issue with Polling in Multibranch Pipeline

• status: Open
  
• priority: Minor
  
• component(s): workflow-multibranch-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 7
  
• imported: 20251212-090250
  

Raw content of original issue

There is general confusing about how polling behaves in multibranch pipeline.  Polling will continue to trigger the same revision over and over again because mutlibranch is pinned to the revision found in computation. 


For now we should disable the trigger in properties step of a multibranch pipeline.


The recommendation for users not using webhooks would be to configure the "Periodically if not otherwise run" but this will add more api calls.