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. 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.
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.
- Shane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
