Perforce Defect Tracking Integration Architecture

1. Introduction

This document describes the architecture of the Perforce Defect Tracking Integration.

This document is incomplete. It is intended as a brief introduction to the architecture for version 0.1 of the P4DTI product.

This document will be modified as the product is developed.

The intended readership of this document is product developers.

This document is not confidential.

2. Overview

The architecture of the integration divides into two parts: the replicator and the tracker-client.

The replicator is a process which copies (replicates) data between a defect tracker and a Perforce server in order to keep each one up to date with changes made in the other. This allows developers to do their routine defect resolution work entirely from their Perforce client, without needing to use the defect tracker's interface. It also allows developers to relate their changes to defect tracking issues.

The tracker-client is an extension to the defect tracker's interface which allows it to act as a Perforce client. This allows developers to do their routine defect resultion work entirely from the defect tracker's interface, without needing to use an ordinary Perforce client.

The replication and tracker-client combination was chosen as the architecture for the P4DTI project after a careful analysis of several alternatives [RB 2000-06-22].

3. The Replicator

Data needed to meet the integration requirements is stored in both the defect tracker's database and Perforce's database. In practice, this is:

• issues and issue fields relevant to developers (stored as jobs) [req?];
• the relation between issues and files [req?];
• the relation between issues and changelists (stored as fixes) [req?]; and
• users and other security information [req?].

A process establishes and maintains consistency between the two databases, copying data back and forth as needed. See figure 1.

Figure 1. The replication architecture

Queries from the defect tracker's interface can be resolved using only the defect tracker's database. Queries from Perforce's interface can be resolved using only Perforce's database.

4. The Tracker-client

The defect tracking client is also a Perforce client. The defect tracking client connects to the Perforce server using the Perforce API. It provides an interface through which the user can carry out routine software configuration management tasks from the defect tracker's interface. See figure 2.

Figure 2. The Tracker-client architecture

A. References

B. Document History

Copyright © 2000 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 copies and derivative works of this document provided that (1) you do not charge a fee for this document or for its distribution, and (2) you retain as they appear all copyright and licence notices and document history entries, and (3) you append descriptions of your modifications to the document history.