| We saw this issue too (Jenkins ver 2.190.1) In our case, it turned out to be caused by the Jenkinsfile referring to a shared lib version (using @Library annotation) that was not at the HEAD of the shared lib repo. Even when there were no changes on the main repo, the PollSCM trigger would detect changes on the shared lib repo, and trigger a new build (using the annotated shared lib version as expected) on each poll. We worked around the issue by removing the pollSCM trigger from the Jenkinsfile, and instead configured the (multibranch) job with "Periodically if not otherwise run" in the "Scan Multibranch Pipeline Triggers" section. |