P4DTI issue job000393

TitleIf you specify the wrong Bugzilla version, P4DTI carries on anyway
Statusclosed
Priorityessential
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionIf you specify an incorrect value for the bugzilla_version configuration parameter, the P4DTI carries on trying to replicate, but fails.
AnalysisSee [1] for the effects.
Much the simplest solution is to drop the bugzilla_version configuration parameter and use the version we detect in the database. Then there's nothing to get wrong.
This means that we don't support organizations who are using Bugzilla version X but have customized it so that our version detection algorithm incorrect detects version Y. I suspect that there are very few such organizations (possibly none) and it won't do any harm to wait for one to turn up before we worry about this. (The best way to support such organizations would be to improve the accuracyt of the version detection algorithm rather than complicating the configuration.)
How foundmanual_test
Evidence[1] <http://info.ravenbrook.com/mail/2001/09/21/17-16-58/0.txt>
Observed in1.1.6
Introduced in1.1.6
Created byGareth Rees
Created on2001-09-24 13:21:49
Last modified byGareth Rees
Last modified on2001-12-10 19:56:25
History2001-09-24 GDR Created.

Fixes

Change Effect Date User Description
22657 closed 2001-09-25 12:16:44 Gareth Rees Removed the bugzilla_version configuration parameter. The Bugzilla integration relies on the version it detects in the Bugzilla database.