Ravenbrook / Projects / Perforce Defect Tracking Integration / Project Documents

Perforce Defect Tracking Integration Project

Evidence for job000335

Gareth Rees, Ravenbrook Limited, 2001-06-18

1. Introduction

This document lists the files needed to reproduce job000335.

2. Evidence

tmtrack.mdb Sample database, created in TeamTrack 4.5, used to test the P4DTI, converted to TeamTrack 5.0 (build 5024c), then converted again to TeamTrack 5.0 (build 5029b).
teamtrack.dll Python interface to TeamTrack 5.0 beta, built using the TeamShare API sent to us by John Keller on 2001-06-06, updated with John McGinley's TSSocket fix for job000328 sent on 2001-06-15. (Sorry, this is the best description I can come up with of the API I'm using.)
job000335.py Python script that illustrates the bug. (You'll need to change the hostname in the connect() call if the TeamTrack server is on a different machine from the client.)

To reproduce the defect:

  1. Set up TeamTrack 5.0 (build 5029b) using the TeamTrack web sever and tmtrack.mdb database.
  2. Set up TeamTrack 5.0 beta (bbuild 5024c) using the tmtrack-5024c.mdb database.
  3. Run Python 2.0 on the same machine, in a directory with the teamtrack.dll and job000335.py files.
  4. Type import job000335.

A. References

B. Document History

2001-06-18 GDR Created.

Copyright © 2001 Ravenbrook Limited. This document is provided "as is", without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this document. You may make and distribute verbatim copies of this document provided that you do not charge a fee for this document or for its distribution.

$Id: //info.ravenbrook.com/project/p4dti/doc/2001-06-18/job000335/index.html#3 $

Ravenbrook / Projects / Perforce Defect Tracking Integration / Project Documents