I should be getting a new server next week, which should speed up the builds and maybe allow us the opportunity to setup some kind of build/test server.
Something we might think about is building the entire project on variations of 1.3.x, 1.4.x, and 1.5.x. As well as have cactus tests run in 2.3, and 2.4 on each of the previously mentioned jdks (or at least those that apply). Not just that, but also run on a few various containers (Jboss, WS, WL) ???
Your thoughts?
-- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED]
----- Original Message ----- From: "Craig McClanahan" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>; "Sean Schofield" <[EMAIL PROTECTED]>
Sent: Friday, April 01, 2005 5:39 PM
Subject: Re: 1.2.x nightlies?
On Apr 1, 2005 2:26 PM, Sean Schofield <[EMAIL PROTECTED]> wrote:> Instead of nightly, a better solution might be to only push a 1.2.x > nightly
> if something changes.
Interesting approach. That is similar to what Anthill does (its an open source tool for doing automated builds.) We use it at work and it builds hourly unless nothing has changed. I wonder how many days go by without a single commit though?
A problem with "push only on changes" is that the Infrastructure folks asked us to install a cron job that deletes nightly build files over "x" days old (currently x=7) to avoid consuming inordinate amounts of disk space. That strategy would have to be reworked for only intermiitten pushes.
In addition, this would seem to violate the definition of what a "nightly build" means, as well as removing any assurance that I have the "latest" nightly build simply by looking at its date.
> James Mitchell
sean
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
