On Thu, 2009-01-01 at 20:28 -0700, Wendy Smoak wrote: > On Thu, Jan 1, 2009 at 7:33 PM, Wes Wannemacher <w...@wantii.com> wrote: > > > So, I'd like to know what people think and if they have suggestions for > > how they'd like to see this done. I'm not steadfastly sticking to Hudson > > at this point, it just seemed easy, so if someone thinks cruisecontrol, > > continuum or whatever might be a better choice, let me know. > > I think it would be better to use the shared ASF Hudson or Continuum > than to start another one. Using the zone to host the example apps > sounds like a good use for it though. > > What was the reason you're not able to change the schedule on the > existing nightly builds? If it's just a matter of getting access, > that should be fixable... >
As far as I could tell, it's launched by a cron job. Cron jobs are owned by their owner. To change it, I'd have to be James or root. To me, this doesn't seem like an optimal way to do it. In Linux, with vixie, anachron or whatever the kids are using these days, the scheduling is more flexible. You can setup daily jobs in /etc/cron.d, or you can do things like @reboot in your schedule. Solaris cron is very traditional. Plus, James' scripts are setup 744, which means only he can make changes. It's not the schedule that I'd like to change, they are "nightly" which suffices to me. But, it is the build itself. I'd like to see struts-2.1.5-snapshot-all.zip available for download. For me, having just core wouldn't do a lot of good as I'd also like conventions and the spring-plugin. Moving it to Hudson would pretty much solve the problem, whether our own or the Apache Hudson. Either way, the job would be setup and we'd all have access to it. -Wes --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
