Pipeline SCM Polling: Break after first "Changes found"
20 views
Skip to first unread message
Stefan Rademacher
unread,
Feb 15, 2018, 10:51:44 AM2/15/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jenkins Users
Hi,
I am running a Jenkins Pipeline, which checks out many repositories (>100). I am using web hooks to trigger Git SCM polling.
Even though the polling is only triggered, if there was a change in at least one of the repositories, the polling puts our Jenkins instance under heavy load (queueing of forked processes for „git ls-remote“).
In average, this would reduce the polling duration by 50%. In the best case, the first repository, which is polled, returns „PollingResult.SIGNIFICANT“. In the worst case, the last repository returns „PollingResult.SIGNIFICANT“.
Am I missing anything? I am not so familiar with the Jenkins sources. What do you think?