I did. I don't see a parameter for <intervalTrigger> to do what I want. The only parameter relevant to <intervalTrigger> is
seconds The number of seconds after an integration cycle completes before triggering the next integration cycle. This does not do what I want. On Feb 29, 11:36 am, Matthias Napalowski <[email protected]> wrote: > There is a setting for that .. > > Just look into the documentation.. > > Regards > > Am 29.02.2012 um 17:34 schrieb Chris <[email protected]>: > > > > > > > > > Say I have continuous integration every 5 mins. Say I have 10 files to > > check in. After I check in my first file, and 5 seconds later, my > > continuous integration just happen to trigger at the 5-min boundary, > > before I check in my other 9 files. How can I set it up so I delay the > > build for a specified amount of time after the first detection of an > > out-of-date or missing file to give me time to checkin my other files? > > Make sense? > > > -chris
