On Tue, Mar 22, 2011 at 5:53 PM, Andrew Kennedy < [email protected]> wrote:
> > On 22 Mar 2011, at 21:42, Rajith Attapattu wrote: > >> * Second, where should the build status emails be sent? The current setup >>> will check subversion every 1 minutes, which has the potential to generate a >>> lot of traffic. I think creating a new mailing list specifically for build >>> output would be most helpful, and I suggest '[email protected]' for >>> this. There is also support for mailing the committer that checked in a >>> change that breaks the build, if people think that would be useful? >>> >> >> I am a little worried about running some of the builds for every checkin. >> That has the potential to send a lot of traffic. >> > > To clarify, Hudson is checking every 15 minutes if there have been any new > check-ins, and then running a build. the maximum build rate is therefore > this frequency. This is configurable using crontab syntax, and could be > changed to hourly or half-hourly perhaps. Currently I set it to: > > */15 * * * * * > > The default profile itself (including system tests) takes around 15 minutes > to run. > > Hourly sounds good. But lets continue with the current setup and see how it goes. We could always change later if we need to. > > How about we run nightly builds (EST) and email the reports to dev list if >> there is a failure. >> > > I was thinking of both, the nightly being a full system test (all profiles) > plus python test kit and release build, generating and publishing artefacts. > > > That will ensure any issues get the attention it deserves immediately. I >> am not so keen about yet another mailing list. >> > > > Andrew. > -- > -- andrew d kennedy ? do not fold, bend, spindle, or mutilate ; > -- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ; >
