This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
bugtracker [2008/07/02 11:02] klette |
bugtracker [2008/07/03 10:37] klette fixed trac rpc stuff. Changed a lot in newer versions |
||
---|---|---|---|
Line 37: | Line 37: | ||
From the bugs panel in launchpad, searching for a bug, and changing its status is 5 mouse clicks, which is quite acceptable. | From the bugs panel in launchpad, searching for a bug, and changing its status is 5 mouse clicks, which is quite acceptable. | ||
As a side note; every edit and change in launchpad is logged and revertable, so we get complete histories for each bug. | As a side note; every edit and change in launchpad is logged and revertable, so we get complete histories for each bug. | ||
+ | |||
+ | == Merging bugs == | ||
+ | Not supported | ||
=== Email interface === | === Email interface === | ||
Line 73: | Line 76: | ||
This enables us to have easy tools on a console level for reporting bugs, and maybe in the future even have automated bug reporting on crashes from nav. | This enables us to have easy tools on a console level for reporting bugs, and maybe in the future even have automated bug reporting on crashes from nav. | ||
- | === Code hosting === | + | === Code hosting/integration === |
Launchpad.net offers code-hosting of tarballs. It also supports mirroring of bzr-branches and svn-branches, but neither of these | Launchpad.net offers code-hosting of tarballs. It also supports mirroring of bzr-branches and svn-branches, but neither of these | ||
apply to us, as we use mercurial. | apply to us, as we use mercurial. | ||
Line 97: | Line 100: | ||
== Managing bugs == | == Managing bugs == | ||
Searching for a bug, entering it and changing it is done 3 mouse clicks. Though with quite a bit of scrolling on the bug page itself on smaller screens. (Tested in 1280x800) | Searching for a bug, entering it and changing it is done 3 mouse clicks. Though with quite a bit of scrolling on the bug page itself on smaller screens. (Tested in 1280x800) | ||
+ | |||
+ | === Mail interface === | ||
+ | Per default Trac only has support for notification emails. Trac does however expose some of its internal api trough python, so it is possible | ||
+ | to write a plugin for it trough /etc/aliases (RT-style). But we'd had to maintain this code ourself. | ||
+ | |||
+ | === RPC interface === | ||
+ | Trac does not have an rpc interface per default, but there is a plugin available that exposes some of the python api. | ||
+ | <code python> | ||
+ | import xmlrpclib | ||
+ | # Connect | ||
+ | server = xmlrpclib.ServerProxy("https://kristian.klette@uninett.no:notmyrealpassword@localhost/trac-dev/login/xmlrpc") | ||
+ | |||
+ | # Report a bug | ||
+ | ticketid = server.ticket.create("My summary", "A description of the problem") | ||
+ | |||
+ | # base64 encode traceback | ||
+ | import base64 | ||
+ | trackeback = base64.b64encode(get_traceback()) | ||
+ | |||
+ | # Add traceback to ticket | ||
+ | server.ticket.putAttachment(ticketid, "traceback.log", "Traceback of the error", traceback) | ||
+ | |||
+ | print "Created ticket", ticketid | ||
+ | |||
+ | </code> | ||
+ | |||
+ | The api it self is quite nice actually, though poorly documented. A rough api-coverage is given at www.track-hacks.org, but only to authenticated users. | ||
+ | |||
+ | === Code hosting/integration === | ||
+ | Trac support code integration of mercurial branches trough a plugin. The plugin is available in debian, so | ||
+ | shouldn't be too hard to get going properly. | ||
+ | |||
+ | === Task management === | ||
+ | Trac differentiates tasks from bugs throug bug-types (one can mark something as a bug, feature request, todo and so forth) | ||
+ | |||
+ | === Price/Licensing === | ||
+ | Newer Trac releases are released under a modified BSD license | ||
==== Roundup ==== | ==== Roundup ==== |