>> - Looking at daemon.conf and TestDirector back-end code, it looks that >> only one QC Project can be managed by the integration daemon. Is that >> correct? > > [Rob] Yes, that is correct - only one Project per ScmBug instance, > otherwise you'd need some form of mapping file to record which > repository maps to which Test Director/Quality Center DB.
We might be able to come up with a syntax in the SCM commit message that would allow to indicate the defect tracking back-end or repository to use. But maybe this not how scmbug is supposed to work today. It would be nice if Kristis or someone else could comment on this. > [Rob] Thanks for the suggestion but doesn't this require access to the > underlying DB? - We currently use the OLE interface. (BTW: I don't claim > to be a QC expert - just picked up the bare minimum to implement the > integration). Also getting that a bug has been modified isn't enough - > we need to check that a particular formatted comment has been added. No, there is no need to have access to the DB. The "Command" object, which is part of Quality Center OTA API allows you to execute simple SQL queries like this, through OLE. To check that a particular field (memo field in QC - like 'BG_DEV_COMMENTS') has been updated, just add AND AP_FIELD_NAME = 'BG_DEV_COMMENTS' to the query I provided earlier. > If you are able to get this sort of thing working I'm sure that > Kristis would be OK to integrate it. I'm not far enough to check what could be done for VDD - I need to get the basics right first. My prototype install is still in progress. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
