Aaron, If I set the quiet period to 2 hours and another code change is submitted then it will reset the quiet period and I might not get a build for several hours. This is what I would like to avoid. I would like it to function normally with a quiet period, but if, for some reason, the quiet period never expires because it keeps getting reset, I want it to build with what it has.
Hopefully that helps to clarify your understanding. Thanks for your input! -Lewis On Thursday, June 14, 2012 5:03:45 PM UTC-7, AaronTC wrote: > > Lewis, > > Can you just set your quiet period to 2 hours? Then no matter how often > commits happen, your code will be built every 2 hours instead of every 30 > minutes. > > Maybe I don't understand what you want to accomplish. > > -Aaron > > On Thu, Jun 14, 2012 at 11:25 AM, Lewis <jenkinsu...@gmail.com> wrote: > >> Does anyone know of a way to limit the number of times a project will >> wait for it's quiet period? >> >> My goal is to ensure that the project will build even it commits keep >> happening. >> >> For example: >> Say my quiet period is 30 minutes, I want my project to build after 2 >> hours even if new code is committed every 20 minutes. >> >> >> Thank you, >> Lewis >> > > > > -- > Aaron Ten Clay > http://www.aarontc.com/ > >
