Is it a job that runs every 5 min or a job that check for changes to the source code control system every five minutes? If the latter, it could be it only finds changes twice that hour or it could be doing the "quiet period" thing and waiting for people to quit making changes for a few minutes. A long quiet period would cause what you describe too.
Lee On Thu, Feb 9, 2012 at 7:50 AM, Wesley Zhang <[email protected]>wrote: > i double checked, the build only took 1 min. > Took 1 min 42 > sec<http://qa-wgyro001.qa.ebay.com/job/v3console-validateInternals/buildTimeTrend>on > qa-ci204 <http://qa-wgyro001.qa.ebay.com/computer/qa-ci204> > > On Thu, Feb 9, 2012 at 6:28 AM, Sami Tikka <[email protected]> wrote: > >> Domi's reply is true. If you really want a new build every 5 minutes even >> if your build takes half an hour (that would be crazy), you can get it if >> you check the "Run concurrent builds if necessary" button. >> >> -- Sami >> >> Wesley Zhang <[email protected]> kirjoitti 8.2.2012 kello 17.59: >> >> > Hi, >> > >> > I set my job runs every 5 mins (*/5 * * * *) but sometimes it was only >> > executed twice within an hour. And in one of the build, i can see the >> > following message. I can understand the triggering method is the timer >> > since i set that. But what does this 9 times mean? The build failed to >> > be triggered by 9 times? or 9 times triggering was merged to this >> > build? >> > >> > Started by timer (9 times) >> > >> > Thank you, >> > BR, Wesley >> > > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
