P4DTI issue job000520

TitleTeamtrack integration does not check that p4dti.reg has been run
Assigned userNick Barnes
DescriptionThe P4DTI Teamtrack integration includes a file called "p4dti.reg", used for modifying the Windows Registry. The modification indicates to TeamTrack that the P4DTI is installed, and that TeamTrack should therefore display Perforce information in the "Version Control History" section of an issue record. The installation procedure [1] includes the necessary instructions for running p4dti.reg. If the administrator does not run p4dti.reg, the "Version Control History" does not show Perforce information. The P4DTI does not check that p4dti.reg has been run. In principle it could perform such a check and generate a suitable warning message. The P4DTI TeamTrack integration is now maintained and supported by TeamShare <http://www.teamshare.com/>.
A customer did not run p4dti.reg, and suggested [2] that the P4DTI could have told him this.
AnalysisPython 2.0+ comes with a module _winreg, which would allow us to examine the registry. But what if the TeamTrack server is on another machine? Then we need to know the name of the other machine (in Windows syntax) and have suitable permissions to read the registry there. This is not easy.
How foundcustomer
Evidence[1] <http://www.ravenbrook.com/project/p4dti/release/1.4.2/ag/#section-5.3.1>
[2] <http://info.ravenbrook.com/mail/2002/05/02/16-41-25/0.txt>
Observed in1.4.2
Introduced in1.0.0
Created byNick Barnes
Created on2002-05-03 11:08:34
Last modified byDavid Jones
Last modified on2003-08-19 13:55:19
History2002-05-03 NB Created.
2003-05-19 NB TeamShare handover.
2003-08-19 DRJ Suspended due to teamshare handover


Change Effect Date User Description
35521 suspended 2002-11-14 13:44:46 Richard Brooksby Removing TeamTrack support from master sources.
Updating project index and FAQ to reflect new TeamTrack situation.