Received: from [10.1.2.49] (root@raven.ravenbrook.com [193.82.131.18]) by raven.ravenbrook.com (8.9.3/8.9.3) with ESMTP id VAA14668; Mon, 29 Jan 2001 21:46:46 GMT Mime-Version: 1.0 X-Sender: gdr@pop3 Message-Id: Date: Sun, 28 Jan 2001 16:03:42 -0800 To: p4dti-staff@ravenbrook.com From: Gareth Rees Subject: Test report for release 0.4.2 from Derek George, 2001-01-26 Cc: Derek George Content-Type: text/plain; charset="us-ascii" ; format="flowed" These are comments from Derek George on the P4DTI. Derek said that he would e-mail his notes. 1. Perforce has no protections for the jobs, so you can't stop Perforce users seeing the jobs (except by replicating to different Perforce servers). Is this limitation documented? The best advice is probably to put confidential information in separate fields that aren't replicated. 2. In order to make the changelist_url feature to work with p4web, you need to set up p4web in browse mode. This isn't obvious: Derek found that by setting up p4web normally (i.e., not in browse mode) it wasn't convenient because you have to log in. So the AG needs some advice on setting up p4web. 3. Derek thinks that there should perhaps be a table giving the purpose of each script that you can run: run.py Run the integration check.py Check consistency refresh_perforce.py Delete Perforce jobs and refresh them 4. When you delete a job in Perforce, it gets restored from TeamTrack but only when it's next changed. It would be nice if it could be restored immediately. (But the deletion doesn't show up in the "p4 logger" output. So how can we do this?) 5. What happens if you delete an issue in TeamTrack? I think the replicator comes up with an error. 6. Will the replicator will be robust as the activity gets busier. Derek would like metrics in the AG: e.g. how long does it take to replicate an issue? how many changes can it cope with per hour? If you have 1000 issues in TeamTrack, how long will it take to refresh perforce? 7. Is there a bug in the job dialog layout algorithm? Sometimes a field will show up on one occasion as a single line and then on another occasion as a multi-line. 8. Changelists always show up as pending in 4407. John says fixed in the next build. 9. "Historical issue" in the AG is a confusing term. 10. NT challenge-response works with a recent API that has the challenge-response fix. Put a note in the AG telling people who use Nt challenge-response with IIS that they need to create a separate virtual directory in IIS that uses TeamTrack authentication (the checkbox in IIS is called "allow anonymous access") and configure the replicator to connect to that. In such a setup, the admin would put this in the config: teamtrack_server = 'server.domain/new_virtual_directory/tmtrack.dll?' (This will work in 0.4.2/4402, but you need to double the slashes because of a bug in the API parsing code.) The new release will be able to work with SSL. If GDR writes a paragraph about this, Derek will check it.