Hi
which version of ccnet are using ?
your setup seems ok to me though
you do mean :
° check every 120 seconds for a change in the code, and do a build
° every hour, do a build regardless of a code change
if so, let me know, because this should work
I use the following which is kind of similar :
<triggers>
<!-- no checking for changes between 22:00 and 06:00 because of
possible system maintenance -->
<filterTrigger startTime="22:00" endTime="06:00">
<trigger type="intervalTrigger" seconds="180" name="continuous"
/>
</filterTrigger >
<!-- force a build on a clean get, so we know that all files are in
source control -->
<scheduleTrigger time="06:00" buildCondition="ForceBuild"
name="Scheduled">
<weekDays>
<weekDay>Monday</weekDay>
<weekDay>Tuesday</weekDay>
<weekDay>Wednesday</weekDay>
<weekDay>Thursday</weekDay>
<weekDay>Friday</weekDay>
</weekDays>
</scheduleTrigger>
<!-- force a build on a clean get, so we know that all files are in
source control -->
<scheduleTrigger time="12:10" buildCondition="ForceBuild"
name="Scheduled">
<weekDays>
<weekDay>Monday</weekDay>
<weekDay>Tuesday</weekDay>
<weekDay>Wednesday</weekDay>
<weekDay>Thursday</weekDay>
<weekDay>Friday</weekDay>
</weekDays>
</scheduleTrigger>
</triggers>
with kind regards
Ruben Willems
On Thu, Apr 15, 2010 at 8:31 AM, Ben <[email protected]> wrote:
> I'd like to have a build either once for every commit, or after an
> hour, whichever is sooner. I've tried adding two interval triggers,
> but only the first appears to be picked up. Do I need to use
> multiTrigger for this? I don't really understand the distinction
> between multiTrigger and the triggers block itself
>
> My triggers block looks like this:
>
> <triggers>
> <intervalTrigger name="Continuous" seconds="120"
> buildCondition="IfModificationExists" initialSeconds="180" />
> <intervalTrigger name="Hourly" seconds="3600"
> buildCondition="ForceBuild" initialSeconds="360" />
> </triggers>
>
>
> --
> To unsubscribe, reply using "remove me" as the subject.
>