gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Gump Wiki] New: GumpDatabase
Date Tue, 10 Aug 2004 17:34:58 GMT
   Date: 2004-08-10T10:34:58
   Editor: AdamJack <>
   Wiki: Gump Wiki
   Page: GumpDatabase

   no comment

New Page:

Gump generates data about the state of interactions of OSS projects, this data is the real
work product of Gump (not the output artifacts stored in it's repositories).

Gump interacts with DBM databases (except on M$ where Python does not support them) and MySQL

== Simple Statistics ==

Gump stores simple 'running counter' type statistics for each GumpEntity. These records have
the following form:

 * Name
 * Successes
 * Failures
 * Prereqs (not done due to pre-requisite failures)
 * datetime of first (success)
 * datetime of last (success) .. i.e. latest.
 * current state (e.g. success)
 * previous state
 * datetime of start of this state
 * sequence (in runs) in this state

If no MySQL database is available Gump uses DBM for these

== Historical Information ==

If a MySQL database is available Gump uses it with the following ["GumpDatabase/Schema"].

On a per GumpEntity basis Gump stores run information:

 * The run GUID
 * The GumpEntity name

'''these two (above) constitute the primary key'''

 * The state
 * The reason code
 * The cause (which other GumpEntity caised grief) 

 * Start datetime
 * End datetime

=== Possible extras ===

 * Number of outputs
 * Total size of outputs
 * Numbers (including totals) of dependees/dependencies

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message