Patrice Domange Posted January 7, 2017 Report Share Posted January 7, 2017 Following the dedicate guide to integrate Bugzilla with SCM, It raise an the error below while testing the connexion: I had copied the plastic.gci script and bugzillaextension.dll (as described in SCM blog, not in the documentation) but the same error is still raised ?!? Quid ? Technical Informations : Windows 10- 64bits, Plastic SCM 5.4.16.802/SQLite, Bugzilla 5.0.3/Strawbery Perl 5.24.0.1/MySql 5.7.17/IIS 10.0.1493.0 Link to comment Share on other sites More sharing options...
calbzam Posted January 10, 2017 Report Share Posted January 10, 2017 Hi, The blog post you mentioned is very old. The files are already included in the client "C:\Program Files\PlasticSCM5\client\extensions\bugzilla". The steps from the guide should enough. The last time we tested the integration was with Bugzilla v4. Could you enable the Palstic SCM client log and attach the output file after reprodicing the issue again? https://www.plasticscm.com/documentation/technical-articles/kb-enabling-logging-for-plastic-scm-part-i.html Regards, Carlos. Link to comment Share on other sites More sharing options...
Patrice Domange Posted January 12, 2017 Author Report Share Posted January 12, 2017 Hi, Please find in attachment the requested log. Regards. plastic20170112-20.log.txt Link to comment Share on other sites More sharing options...
manu Posted January 13, 2017 Report Share Posted January 13, 2017 Hi Patrice, this is the error Plastic is receiving from Bugzilla: Quote 2017-01-12 20:03:58,258 ERROR PlasticThread - Error when performing background operation: Le serveur a commis une violation de protocole. Section=ResponseHeader Detail=Le nom de l'en-tête n'est pas valide 2017-01-12 20:03:58,258 DEBUG PlasticThread - Stack trace: à System.Net.HttpWebRequest.GetResponse() I'm afraid Bugzilla 5 is not supported yet so we'll need to test it and try to resolve the problems. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.