[JENKINS-46536] A pollSCM property in a multibranch pipeline should ignore checking the primary SCM

Context: https://groups.google.com/forum/#!topic/jenkinsci-users/d3RyHNnbieI

User reports that pollSCM is working for SCM changes from the multibranch managed SCM. 

pollSCM should either be a no-op, or only poll secondary SCMs when used in a multibranch project

---
Originally reported by stephenconnolly, imported from: A pollSCM property in a multibranch pipeline should ignore checking the primary SCM

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

Raw content of original issue

Context: https://groups.google.com/forum/#!topic/jenkinsci-users/d3RyHNnbieI


User reports that pollSCM is working for SCM changes from the multibranch managed SCM. 


pollSCM should either be a no-op, or only poll secondary SCMs when used in a multibranch project

Start by tracing how pollSCM is handled for multibranch projects in the branch-api-plugin, using the linked user report as context. Determine how primary and secondary SCMs are distinguished, then add coverage for the reported behavior; done means the primary multibranch SCM is not polled by this property while any intended secondary-SCM behavior remains correct.

Written by the indexing model from the issue text.