| Thu, 06 Aug 2009 18:41:00 +0000 |
dfraser |
After lengthy waiting and no complaints of data loss, add the final step of dropping the old data with witty commentary. See #329
|
| Sat, 16 May 2009 22:39:21 +0000 |
wbell |
Type fixes for Postgres 8.x (we noticed issues on 8.3. Newer versions of Postgres don't auto massage integers from Python to string values in the database. In Bitten, this was causing issues with the 'id' field of bitten_rule, which was actually an integer (coming from the id field of the bitten_platform table.) Without explicitly converting it to a string, you'd see the error reported in #390. Added upgrade steps, tested on Postgres8.3. Closes #390. We may want to rename this field to 'platform' later.
|
| Mon, 16 Mar 2009 17:46:18 +0000 |
dfraser |
Replace `CREATE TEMP TABLE` with the more database-independent `CREATE TEMP TABLE` (thanks Manfred) - Fixes #370
|
| Mon, 16 Mar 2009 12:03:19 +0000 |
dfraser |
Ensure log files are stored and read in binary, not text format (otherwise Unicode gets confused):
|
| Fri, 13 Mar 2009 14:52:51 +0000 |
dfraser |
Support unicode by converting everything to UTF-8 on write and back to unicode on read - should fix #369
|
| Fri, 13 Mar 2009 13:09:49 +0000 |
dfraser |
Fix typo - see #329
|
| Fri, 13 Mar 2009 08:52:47 +0000 |
dfraser |
Switch to storing log messages in files rather than in database rows:
|
| Tue, 07 Aug 2007 11:29:11 +0000 |
cmlenz |
Use reStructuredText as the API documentation syntax.
|
| Tue, 07 Aug 2007 09:49:08 +0000 |
cmlenz |
More restructuring: got rid of the `trac_ext` subpackage, which makes no sense now that the master is also coupled to Trac.
|
| Tue, 07 Aug 2007 08:58:38 +0000 |
cmlenz |
Update file headers and other stuff pointing to the old home.
|
| Tue, 24 Jul 2007 17:32:02 +0000 |
cmlenz |
Use UTF-8 as encoding of source files.
|
| Thu, 05 Jan 2006 16:27:04 +0000 |
cmlenz |
Ported [336] to 0.5.x.
0.5.x
|
| Thu, 05 Jan 2006 16:26:07 +0000 |
cmlenz |
More fixes with interoperability with Trac trunk. Closes #91. Thanks to Sven Reimers for the patch.
|
| Wed, 04 Jan 2006 18:49:34 +0000 |
cmlenz |
Ported [333] and [334] to 0.5.x.
0.5.x
|
| Wed, 04 Jan 2006 18:30:52 +0000 |
cmlenz |
Fixes for compatibility with Trac trunk and 0.9.3.
|
| Sat, 26 Nov 2005 15:00:10 +0000 |
cmlenz |
More docstring improvements.
|
| Mon, 03 Oct 2005 21:15:31 +0000 |
cmlenz |
Store the reason(s) for build step failure in the database.
|
| Mon, 26 Sep 2005 22:49:15 +0000 |
cmlenz |
Fix upgrade for installs with no stored reports. Thanks to Matt Good for catching this.
|
| Wed, 21 Sep 2005 23:06:12 +0000 |
cmlenz |
Some pylint-inspired cleanup.
|
| Tue, 20 Sep 2005 22:16:41 +0000 |
cmlenz |
* Refactoring of build recipes, the file format has changed slightly:
|
| Mon, 19 Sep 2005 15:22:14 +0000 |
cmlenz |
Huge refactoring to remove dependency on BDB XML. Report data is now stored in the Trac database (SQLite/PostgreSQL).
|
| Wed, 14 Sep 2005 18:55:51 +0000 |
cmlenz |
Changes to the BDB XML report store to support transactions. Closes #47.
|
| Mon, 12 Sep 2005 21:59:14 +0000 |
cmlenz |
In preparation for supporting BDB XML transactions, move the report store backend selection away from using Trac extension points, and use a plain Python object instead of a component to represent a store backend.
|
| Tue, 30 Aug 2005 18:56:14 +0000 |
cmlenz |
Fix the BDB XML upgrade procedure: If a document is found that is associated with a non-existing build, just remove it.
|
| Tue, 30 Aug 2005 18:44:55 +0000 |
cmlenz |
* Changed the `IReportStore` interface to allow querying with [http://www.w3.org/XML/Query/ XQuery]. This should make it possible to efficiently query the report store for any existing metrics.
|
| Sat, 27 Aug 2005 07:58:12 +0000 |
cmlenz |
Flip the switch: Bitten is now BSD-licensed.
|
| Sun, 21 Aug 2005 17:49:20 +0000 |
cmlenz |
Build recipes are now stored in the database with the build configuration. This means that it is no longer necessary to store the recipe in the repository. Closes #41.
|
| Thu, 04 Aug 2005 20:15:39 +0000 |
cmlenz |
* Store build logs in a structured way, for example to highlight messages on the error stream.
|
