One thing that is possible to do in Python that would have been
difficult to do in shell script is to parallelize some of the processing.
In a daily build, there are three major components: cvs/svn update,
copy/rsync, and build. My recommendation would be to not overdesign
this (too many
On Thu, 25 Mar 2004, Leo Simons [EMAIL PROTECTED] wrote:
Traditional gump has this architecture.
On completion, some other script files are or can be run to do some
other things (like send out failure notifications).
which is done by a Perl script, which just adds to the tool mix of
Leo Simons wrote:
snip/
As for the buzzwords...let's create an action-based, data-centric,
graph-based, versioning-enabled, highly componentized, extensible,
continous integration system.
I have no idea how to do any of that in python, but it sounds like fun
to find out..
I had thought
Leo Simons wrote:
(did I mention I'm an avalon guy? :D)
did I mention that Avalon is dying out of flexibility cancer?
Dude, let's just fix things incrementally.
Lazyness is a virtue and Darwin is your man.
--
Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
Stefano Mazzocchi wrote:
Leo Simons wrote:
(did I mention I'm an avalon guy? :D)
did I mention that Avalon is dying out of flexibility cancer?
Yes Stafano ... I've been watching your predications.
Stephen.
--
||
| Magic by Merlin
