gumpy.py -- cron wrapper.

["Adam R. B. Jack" <aj...@trysybase.com>]

I worked a little on gumpy.py -- a front end to running a full integration
using Gumpy, typically from cron. This is a replacement for gumpy.[sh|bat].

Roughly, what it needs to do is the following: (1) not use any Gumpy
classes. (2) clear old Gumpy *.pyc files [not done yet] (3) update Gumpy
from CVS (4) set PYTHONPATH & run integration (5) display log/output files
[if things don't work]. Maybe it does some environment checks also.

Amazingly perhaps (if not to me, I've got scars) Python isn't always as easy
to write as a shell script, especially for launching other things. Still, I
am making some progress.

What isn't there is a way to locally configure this script. I'm wondering
what folks thoughts are, and what folks preferences are. Do you think I
ought parse the workspace XML file [not using Gumpy classes], and extract
all info from there? Ought I check the environment or commend line? I know
this is programming 101, but I'd like input on what folks think would be the
most manageable.

regards,

Adam
--
Experience the Unwired Enterprise:
http://www.sybase.com/unwiredenterprise
Try Sybase: http://www.try.sybase.com

Re: gumpy.py -- cron wrapper.

["Adam R. B. Jack" <aj...@trysybase.com>]

> > Do you think I ought parse the workspace XML file [not using Gumpy
> > classes], and extract all info from there?
>
> If all information you need is in there anyway, I'd say yes.
> Otherwise the two sets of configurations would soon run out of sync.

If it isn't all there, it probably should be. I agree, read the workspace.

I found a simple DOM parser in Python that allowed me to set variables from
attribute values, so I could extract basedir and such from the workspace. It
also extracts mail stuff (added w/ Gumpy) so it can mail failed logs to the
owner. I don't think it needs much more.

The replacement for gumpy.bat|sh is coming along, although I'm not quite
ready to switch LSD to it. It needs to clean *.pyc (important for when Gumpy
get's refactored between runs) and it needs [IMHO] to copy forrest output
(for days when that fails) but then I think it'll be ready.

(As CVS logs no doubt showed, I got distracted from this 'cos of the desire
to make Gumpy more portable, and remove cat/ls usage.)

regards

Adam

Re: gumpy.py -- cron wrapper.

[Stefan Bodewig <bo...@apache.org>]

On Mon, 23 Feb 2004, Adam R. B. Jack <aj...@trysybase.com> wrote:

> Do you think I ought parse the workspace XML file [not using Gumpy
> classes], and extract all info from there?

If all information you need is in there anyway, I'd say yes.
Otherwise the two sets of configurations would soon run out of sync.

Stefan