----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 21, 2001 2:18 PM
Subject: Re: [gump][cactus] problems with nightly zips
> Good question - I still haven't delved into exactly which code in Gump
> physically posts results from the nightly build. However I disagree that
> the only thing you may want posted is the official 'dist' result of a
> project.
>
> I view gump as more of a development tool than an end-user-distribution
> serving tool. The real value for our project is that we know every day if
> the build compiled and if our project's self-defined set of 'smoketests'
> passed or not. We can then see if one build fails, by looking at the gump
> CVS updates which files were changed between that build and the previous
> one, and thus what likely caused problems.
>
> A 'dist' result may be one thing various projects want posted, yes. But
> I'm far more interested in seeing the results of any tests zipped and
> posted, and actually getting a zip/tar.gz of the whole development tree
> as-is, both plain src and classes directories.
Good for you, but I am far more interested in pleasing my end users ! :-)
(see below). I know the date of the GUMP build and I can do an update of my
src on that date and redo the build if I need.
> That way if there is a
> problem, I should be able to download the posted project from the gump
> area, and have the exact project tree that caused the compile error/test
> problem/whatever.
>
It is good if Gump does more rather than less. However, I'd like to use Gump
at least to :
* know if a dependency is breaking anything,
* deliver the distributables to nightly area so that end users (and not
developers) can use the latest features and bug corrections.
Now, if it does more than this and package the full directory and make it
available somewhere for debugging, then good, but I need at least the
distributables packages as the user expect them. Also the src are indeed
copied and generated in Cactus dist area. I think you should have a look
there, you'll that there is everything.
> Do we have a start on getting reccommended standards for integration with
> Gump and it's nightly posting? I thought by default Sam simply zipped the
> whole project tree up when done, since that should include everything.
> I've started to update Xalan to have some of the specific .zips I'd like
> created (since I can make them a bit smaller than the whole tree) but
> haven't yet tried to ask Gump to copy those instead of just zipping the
> whole thing.
I would say that a good practice would be for GUMP to at least take files
generated in the dist area of the project but these files should be listed
as part of the GUMP project definition. Then if GUMP wants to do any
additional steps (like zipping the full tree), then it is up to it.
Thanks for your help.
-Vincent
> - Shane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
