[p4] Recommendations for Defect Tracking Solutions

[Lewis Baker]

perforceuser at spamex.com wrote:
> What are your recommendations for a good defect tracking solution to  
> work with Perforce?
> 
> I like Trac, but it won't work with Perforce (I need something more  
> than the hacked plugin). It also doesn't seem to scale particularly  
> well.

We use Trac as our defect tracking solution and have developed a new
Perforce plugin for Trac inhouse that seems to be more scalable than the
existing Trac plugin. We are currently using it successfully on a
repository of around 80000 changes.

The plugin uses Trac's SQL backend to cache some changelist information
so that markup of wiki changelist links and Trac's timeline doesn't have
to go back to Perforce every time or have the entire Perforce metadata
in memory. When it does have to go out to Perforce it uses the
PyPerforce interface.

Trac's source browsing and file and directory diffs make quite a useful
tool for interrogating a Perforce repository, comparable to

We haven't gotten around to adding P4DTI-style integration between
Perforce jobs and Trac tickets yet but it's something we're looking to
do in the near future.

I'm not sure if I can publish the source for the plugin yet but if
enough people are interested then I can certainly investigate releasing
it as open source.

Cheers,
Lewis.

-- 
Lewis Baker                                               I-SiTE
Software Engineer                               3D Laser Imaging
Email  : lewis at isite3d.com.au         http://www.isite3d.com.au/