Unfortunately it typically happens, as there could be more than one push in between the Git plugins polling intervals. I worked in teams from 50 up 80 people (actually organised in scrum-teams of around 10 members each) and guarantee that it happens :-)
The problem then is to associate the broken build with one of the members (or even teams) ... with the risk of leaving the ball to fall in a no-man's land ;-( Luca. On Tuesday, December 31, 2013 7:14:49 PM UTC, Jesse Glick wrote: > > On Wed, Dec 25, 2013 at 5:48 AM, Luca Milanesio > <[email protected] <javascript:>> wrote: > > I am looking at the new Jenkins Validated Merge plugin from Cloudbees > > This is probably better sent to e.g. [email protected] <javascript:>, > but briefly: > > > If you have a build that includes 5 commits by 5 different people > > That would not generally happen, assuming each person pushed their own > commits as they did them; each such push produces a separate build. If > one person pulls commits from others (or uses git-am, etc.), and > pushes them all at once, then just one build will run, so if you want > to figure out the cause of a failure in that build, use git-bisect as > usual. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
