For reference I'm on Jenkins 1.601 with Perforce Plugin v1.3.27. I have a polling interval set for H/5 * ... for Perforce SCM changes on a Job in Jenkins. I also have enabled concurrent builds for the job.
If multiple checkins occur during the polling interval then multiple instances of the Job are started. The odd part is one job has all of the changes and the others are no different than the first. What I would like to see is either one job started for each changelist (so they all get verified with tests) or one job started for all changes submitted in the interval only. It seems like either solution would require a separate job to poll Perforce then run a script to analyze the changes and spin up any other job(s) rather than relying on the Perforce SCM Plugin + Jenkins internal logic. Is this correct? Thank you, Brent -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1249c8c3-d08f-438d-b24c-e5d5b275e56d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
