[ http://issues.apache.org/jira/browse/GUMP-66?page=comments#action_63100 ] Leo Simons commented on GUMP-66: --------------------------------
An easier way to implement this would be to run a cronjob every few minutes that checks for a lockfile, and if one doesn't exist, have that cronjob kick of the new build run. That requires reliable locking of course. > Run gump as a service > --------------------- > > Key: GUMP-66 > URL: http://issues.apache.org/jira/browse/GUMP-66 > Project: Gump > Type: New Feature > Components: Python-based Gump > Versions: Gump2 > Environment: Brutus (and similar) > Reporter: Adam Jack > Fix For: Gump3-alpha-5 > > Currently Gump runs from cron, at intervals, *if* Gump is not still running > (from a previous run). This is somewhat haphazard, and a waste of spare > cycles. Gump needs to be able to be run continuously, starting a new run a > soon as the last has completed. This seems like some sort of 'service' > script, but it is likely OS specific. > The script that runs this countinuously could call gumpy.sh (or gumpy.py) and > launch runs with varied commandline parameters. For example, it could make > every Nth run an official run, or make N-1 'optimized' (only compile if > something changed) and the Nth full, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
