[JIRA] [schedule-build] (JENKINS-23625) SCM Trigger polling efficiency can be improved massively with a trivial change

[richard.cl...@cdl.co.uk (JIRA)]

richard clegg created JENKINS-23625 SCM Trigger polling efficiency can be improved massively with a trivial change Issue Type: Improvement Affects Versions: current Assignee: Andreas K Attachments: ScmtriggerExcerpt.txt Components: schedule-build Created: 30/Jun/14 2:11 PM Description: SCMtrigger checks to see if any changes have been made to the SCM and if so schedules a build. When it schedules a build it checks to see if a job has already been queued and just assigns the trigger to an existing queued build if it finds one, otherwise it creates a brand new queued job. This is ok except if several scm triggers arrive all at once and they all start polling the scm, duplicate queued requests get created needlessly if queued jobs haven't started or they haven't finished fetching the changes into the workspace. The scm trigger should be altered to check if a job is already queued before polling and then just ignoring the new polling request as the already queued job will process it. this will save a lot of processing time and also prevent duplicate triggering that we are seeing on our system. The code excerpt from SCMTRigger to change is attached... Environment: Any Fix Versions: current Project: Jenkins Priority: Minor Reporter: richard clegg

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.