struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Cooper <mfncoo...@gmail.com>
Subject Re: Nightly builds
Date Thu, 22 Sep 2005 04:17:17 GMT
On 9/21/05, James Mitchell <james.l.mitchell@mac.com> wrote:
>
> My goal is to have the sources for both 1.2.7 branch and HEAD in such
> a way that if Infra decides to zap the zones, that I can just flip on
> my cron job again and poof (just as quickly) we are back in business.


Right. My point was that we'd have lost a week's worth of nightlies, so if
there are problems with the latest one, we can't tell people to pick up one
from a few days ago. But maybe we don't care enough about that to worry
about it.

--
Martin Cooper


I'm half way there. The 1.2 branch build is complete, and now being
> built and uploaded from the zone to minotar (the normal nightly spot)
> using my account. It is still not automated (crontab), but it's
> there. And let me just say, that machine simply screems! I can do a
> full release of the 1.2 branch in about 35 seconds (not counting
> download-dependencies). It was at about 3 or 4 minutes on my linux box.
>
>
> For HEAD, this means getting the maven build streamlined, which I've
> already done some work on, but things could be even faster. I'll
> keep plugging away, but be aware that someone is bound to notice the
> missing nightlies for 1.3.x.
>
>
>
> --
> James Mitchell
> Software Engineer / Open Source Evangelist
> Consulting / Mentoring / Freelance
> EdgeTech, Inc.
> http://www.edgetechservices.net/
> 678.910.8017
> AIM: jmitchtx
> Yahoo: jmitchtx
> MSN: jmitchell@apache.org
> Skype: callto://jmitchtx
>
>
>
>
>
> On Sep 21, 2005, at 1:40 PM, Martin Cooper wrote:
>
> > On 9/20/05, James Mitchell <james.l.mitchell@mac.com> wrote:
> >
> >>
> >>
> >> I have finally gotten around to finishing the setup of my account on
> >> our zone (http://www.apache.org/dev/solaris-zones.html) and thanks to
> >> Martin and Google, I'm now able to fully build the nightly (by hand)
> >> of the entire Struts project.
> >>
> >
> >
> > Woohoo! :-)
> >
> > For those who haven't been watching, the nightly builds that were
> >
> >> happening on my machine began failing during the 'svn up' portion of
> >> the script. This basically caused Maven do say "oh cool, nothings
> >> changed, let's not build any artifacts", and the rest of the shell
> >> script just happily uploads the same jars from the last build. This
> >> explains the mismatch in date/name of some of the nightly artifacts.
> >>
> >> So, where are we?
> >> Currently, the latest build (nightly) is available here (http://
> >> struts.zones.apache.org/~jmitchell/nightly/)<http://struts.zones.apache.org/~jmitchell/nightly/)>
> <http://
> >> struts.zones.apache.org/~jmitchell/nightly/)<http://struts.zones.apache.org/~jmitchell/nightly/)>
> >.
> >> I also updated the
> >> readme on the regular nightly download page to point to this interim
> >> spot. This is a manual process right now.
> >>
> >>
> >> Where do we want to be?
> >> Typically, nightlies are hosted from /www/cvs.apache.org/build/
> >> {project}.
> >> Right now, both Craig and my own personal machines are configured to
> >> pull from cvs/svn, run the build, and upload something to that
> >> location. This can only happen as a cron job if we copy the
> >> appropriate ssh keys to the target server (no login prompted).
> >>
> >> The question really comes down to "Where will the nightlies live?".
> >>
> >> If we want to use some generic account on the zone to build the
> >> nightly, the script would need to either:
> >> a) use someone's account (mine?) to build/scp the nightlies over to
> >> cvs.apache.org <http://cvs.apache.org> <http://cvs.apache.org>
> >> b) build via a generic account and scp via a valid account (committer
> >> account on the zone)
> >>
> >> Although, we can actually avoid all of this by just hosting the
> >> nightlies from the zone. The url might look like this:
> >> http://struts.zones.apache.org/~nightly/
> >>
> >
> >
> > As Craig mentioned, the zones are, in theory, still subject to
> > disappearing
> > in a puff of bits, so I'd prefer to see the nightlies pushed to
> > minotaur so
> > that they're still around if that does ever happen. I think we
> > should have a
> > 'build' account on the zone that does the actual building; I don't
> > have any
> > good ideas on the key to use to push them over when they're done.
> >
> > That said, with Justin and Leo both stepping back from infra@, and
> > several
> > others being, uh, less prominent than they used to be, it's not
> > clear that
> > much of anything is going to happen on the zones machine in the
> > near future
> > that would disrupt us.
> >
> > If we do distribute from the zone itself, it would be nice to have
> > a URL
> > more like:
> >
> > http://struts.zones.apache.org/builds/nightly
> >
> > rather than actually exposing an account name in the URL. ;-)
> >
> > --
> > Martin Cooper
> >
> >
> > Somewhat related - Craig, if you are interested, I'd be happy to help
> >
> >> you move your nightly Ant builds to the new zone.
> >>
> >>
> >>
> >> --
> >> James Mitchell
> >> Software Engineer / Open Source Evangelist
> >> Consulting / Mentoring / Freelance
> >> EdgeTech, Inc.
> >> http://www.edgetechservices.net/
> >> 678.910.8017
> >> AIM: jmitchtx
> >> Yahoo: jmitchtx
> >> MSN: jmitchell@apache.org
> >> Skype: callto://jmitchtx
> >>
> >>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message