In most Jenkins' examples the SCM poll value is designated */15 * * * *, ie. poll SCM every 15 minutes. That's fine when you have hundreds of jobs, but not if you have thousands of jobs as it results in thousands of request to the SCM (Subversion in this case) server at 15, 30, 45, and 0 minutes past the hour.
Is there some way to randomize the polling value in Jenkins so as to avoid the above scenario?
On the Jenkins master configuration screen there's a value Max # of concurrent polling. Should this be set (and to what value) to avoid the above scenario?