Hi you may make an issue, but there is a working alternative, so I do not think anyone will take the time soon to look at it there are more important issues we need to fix / take a look at
anyway, I updated the log in the 1.5 and trunk, so it also shows the triggername when a build is enqueued, and if available, the user who forced the build. Should make it easier to pinpoint stuff. with kind regards Ruben Willems On Thu, Apr 15, 2010 at 9:41 PM, Ben <[email protected]> wrote: > > > On 15 Apr, 20:08, Ruben Willems <[email protected]> wrote: > > Hi > > > > I see the same behaviour > > so it's probably due to the 2 interval triggers, I'll try to find out > why, > > but not promisses > > Changing to a multitrigger will not help, since the triggerblock is in > fact > > a multi trigger behind the scenes > > > > Thanks for the quick diagnosis. Do you want me to log an issue, or > have you already done that? > > > So solve your problem I would add X schedule triggers > > > > <intervalTrigger name="Continuous" seconds="120" > > buildCondition="IfModificationExists" initialSeconds="180" /> > > <scheduleTrigger time="08:00" buildCondition="ForceBuild" > name="Scheduled"> > > <scheduleTrigger time="09:00" buildCondition="ForceBuild" > name="Scheduled"> > > <scheduleTrigger time="10:00" buildCondition="ForceBuild" > name="Scheduled"> > > > > and so on > > > > We'll give that a go. We'll keep up to date with patches, so hopefully > we'll pick up a fix > > Thanks for all your help! > > > this will have the desired effect, and also have more control on the > exact > > timings > > so you know that the build will be exaxt at every hour > > > > with kind regards > > Ruben Willems > > > > On Thu, Apr 15, 2010 at 10:45 AM, Ruben Willems <[email protected] > >wrote: > > > > > > > > > Hi > > > > > in ccnetLog will be a log when a trigger has fired, but there will not > be a > > > log when a trigger was not fired. > > > so maybe you can find something in the log. > > > > > I'll try to test this in the 1.5 branch > > > > > with kind regards > > > Ruben Willems > > > > > On Thu, Apr 15, 2010 at 8:59 AM, Ben <[email protected]> > wrote: > > > > >> On Apr 15, 7:54 am, Ruben Willems <[email protected]> wrote: > > >> > Hi > > > > >> > which version of ccnet are using ? > > > > >> We're using 1.5.0.6237 > > > > >> > 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 > > > > >> Yes, this is what we're trying to do. Some of our unit tests have > > >> exhibited possible instability, so I'd like to run the tests often, > > >> regardless of any check-ins, while still having fast response to > check- > > >> ins. Could it be the combination of two interval triggers that's the > > >> problem? I notice you only have one interval trigger below. > > > > >> Is there anyway to get a log of then triggers are checked, and why > > >> they are or aren't triggered? > > > > >> Thanks for the prompt reply! > > > > >> Cheers, > > >> Ben > > > > >> > I use the following which is kind of similar : > > > > >> > .... > > > > >> -- > > >> To unsubscribe, reply using "remove me" as the subject.- Hide quoted > text - > > > > - Show quoted text - >
