On 6/19/06, James Mitchell <[EMAIL PROTECTED]> wrote:

Wonderful timing, I was just about to start a new thread wrt getting
the nightlies back online.  And so I'll move my thoughts here.

----
So, with the mini hackathon out of the way, and our new buddy
MrStruts taking care of the continuous integration for us (ok, he
isn't doing much right now, but he is there and ready to roll), I'd
like to turn at least some of my attention to getting the nightlies
back online.  Sorry if this was already discussed/decided on a
different thread, I'm behind on every list I am currently subscribed
to, except [EMAIL PROTECTED]

I plan to have MrStruts do full nightly builds using a similar
nightly script to the one I was using for many months with the Maven
1 built nightlies.  I'm in the process (as I type this) of creating
the necessary build scripts to produce nightly artifacts of Struts
Action 1 (1.2.x and 1.3.x), Struts Action 2, and Shale.

Currently, we publish the nightlies here:

  http://people.apache.org/builds/struts/

...and I see Craig has begun publishing Shale nightlies to this spot:

  http://people.apache.org/builds/struts/maven2/shale/

So, on that note, I'll begin publishing Action 1 and 2 nightlies in a
(almost) similar fashion.

Craig, I've already zapped the 'maven' directory, can we:
1. remove the extra directory 'maven2' and just have p.a.o/builds/
struts/shale (requires you to change your scp script)?
2. rm -fr 'nightly' from the same dir?


Not a problem ... I'll switch for tonight's build.  Indeed, I hadn't
announced the destination until we had a chance to coordinate across the
various builds.  I published my shell script from before this change in an
earlier response to Wendy's questions ... it's four simple substitutions.

So, (high level) we would have:

http://people.apache.org/builds/struts/shale
http://people.apache.org/builds/struts/action1/1.2.x/
http://people.apache.org/builds/struts/action1/1.3.x/
http://people.apache.org/builds/struts/action2
http://people.apache.org/builds/struts/tiles   (eventually)

...and each directory (Maven 2 built) would have a directory for the
particular module, which would have the current jar, war, or zip, and
6 days prior.


How does this sound?


Sounds good, but I've got some additional thoughts that I would like to see
us implement consistently.

* In addition to publishing artifacts in this directory, I'm also updating
 the snapshots for all the poms and jars.  That way, people who like
 to live dangerously :-) and have dependencies on the HEAD code
 effectively get daily updates, without having to manually check out
 the sources and rebuild them.

* I succumbed to my historical habits :-) and produced both .zip and
 .tar.gz versions of the artifacts.  I'd be open to publishing only in zip
 format since it's pretty universal, and we don't particularly care about
 file permissions in what we publish (i.e. no executables to worry
 about).

* I'm really happy with the way that the assemblies constructed by the
 Shale build scripts (both for the framework itself, and for each
individual
 sample app) are themselves buildable if you have Maven2 installed.
 This kind of thing will encourage others to get on the bandwagon (listen
 to me, the latecomer :-), even if they don't want to try to download and
 build the framework itself from Subversion.  I'd like to see this approach
 implemented consistently across our artifacts.

* I'm not so happy with the lukewarm support Maven2 currently offers for
 integration testing.  Wendy got inspired by some comments on the user
 mailling list for Maven, though, and created a nice workaround in the
 poms for the Shale sample apps.  If you do something like:

   mvn install -Pitest

 then you can run the system integration tests built into the same project,
 rather than having to set up a parallel project for those tests.  Shale's
 integration tests happen to be built with HtmlUnit, but it should be
equally
 feasible to use Canoo or whatever else you like.  We're also leveraging
 the Cargo plugin to even start and stop your favorite container for you.

Craig



Wendy wrote:
> That was a few days ago. :)

Yes, I know, I never got back to this.  Sorry, it's been a heck of a
month this week ;)  My questions would have been about the POM
changes that Sean eluded to during our mini hackathon.  I could be
wrong, but I thought he said there would be an issue with something
we needed and it not being published yet and that may or may not have
stemmed from a private conversation you may or may not have had over
IM.  Sorry, the details are still a little cloudy.  Forget about it
for now, I'm sure if it's a problem we'll know as soon as we begin
adding more projects to Continuum.


--
James Mitchell




On Jun 19, 2006, at 9:20 PM, Wendy Smoak wrote:

> On 6/14/06, James Mitchell <[EMAIL PROTECTED]> wrote:
>
>> Yes.  There is a wiki page for this as well.
>> http://wiki.apache.org/struts/StrutsContinuum
>>
>> It's a work in progress, and I'm about to head out, but I'd like to
>> ask Wendy a few questions wrt pom, parent-pom, snapshot vs. released,
>> etc, etc.
>>
>> Back in a bit.
>
> That was a few days ago. :)
>
> Craig, are you ready to get Shale set up on Continuum?  I assume you'd
> like to get out of the nightly builds business, and have them run from
> the zone.
>
> In another thread, I think Sean mentioned it's ready to start
> adding things.
>
> I started to update the Shale site yesterday, but I need to know where
> the nightly builds/snapshots are going to be so I can link to them.
>
> Thanks,
> --
> Wendy
>
> ---------------------------------------------------------------------
> 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]


Reply via email to