|Title||No automatic check of configuration|
|Assigned user||Gareth Rees|
|Description||How do you tell if the configuration is correct? There should be automatic checking of the configuration.|
See e-mail "Checking the configuration automatically" for some ideas.
|Analysis||The replicator shouldn't assume that the configuration is correct, but should check it.|
We could have an external checking script that does a really thorough job.
See also GDR's list of things to check at <
The replicator should check aspects of the TeamTrack workflow, as described in section 3.2 of the AG; when problems are discovered it should give a warning, and the warning should appear in section 13.2 of the AG. GDR 2001-01-02.
|Created by||Richard Brooksby|
|Created on||2000-11-23 14:12:32|
|Last modified by||Gareth Rees|
|Last modified on||2001-12-10 19:03:34|
|History||2000-11-23 RB Created from sources (see evidence).|
2001-01-02 GDR Added note about workflow checks.
|7565||closed||2001-01-23 18:16:58||Gareth Rees||Adding unmatched_users method to TeamTrack user translator.|
|7554||open||2001-01-23 16:28:30||Gareth Rees||The function check_email() now checks that the address is an RFC822 address spec.|
|7552||open||2001-01-23 16:01:40||Gareth Rees||The p4 module now checks that Perforce client version is supported.|
|5348||open||2000-12-04 10:07:54||Gareth Rees||Check that replicator's RID and defect tracker's RID match.|
|5127||open||2000-11-29 18:51:18||Gareth Rees||Fixed bug: error changed to self.error.|