[ http://issues.apache.org/jira/browse/GUMP-26?page=all ] Leo Simons closed GUMP-26: --------------------------
Resolution: Won't Fix Fix Version: Gump3-alpha-3 (was: Gump2) Gump3/Dynagump will store historical data in a database. > keep around build logs > ---------------------- > > Key: GUMP-26 > URL: http://issues.apache.org/jira/browse/GUMP-26 > Project: Gump > Type: New Feature > Components: Python-based Gump > Versions: Gump2 > Reporter: Leo Simons > Fix For: Gump3-alpha-3 > > Java gump used to keep around 5 days worth of build reports. We should have > something similar in gumpy, with the last five days kept in full, and perhaps > the last five weeks, and the last five months (ie your average backup > schedule policy). Maybe we can do compression using diffs, but not sure what > is the right space/computation tradeoff. We could put the logs in svn :-D -- 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]