http://bugs.grommit.com/show_bug.cgi?id=496
Summary: DbLookups should consider following RTIstatus with
RTIget
Product: SCM Migration
Version: unspecified
Platform: All
OS/Version: Solaris 11/Nevada
Status: NEW
Severity: enhancement
Priority: P3
Component: rtichk
AssignedTo: scm-migration-dev at opensolaris.org
ReportedBy: Mark.J.Nelson at Sun.COM
I'm splitting this off from 457:
Rti.py:88
Does this mean we ask webRTI for the same RTI N times, if that RTI
contains all N bugs in our comments? Surely there's no need?
(or does the code in DbLookups.Rti really suggest it doesn't list
all CRs under that RTI, when queried that way?)
So it turns out that webrticli really DOES return only one bug id in an
RTIstatus call. You then need to take the RTI number and product fields
returned from RTIstatus, and use them with RTIget to request a complete
buglist.
So we're talking a minimum of two calls to webrticli, so we don't break even
until we're processing at least three bugids. And if the bugs in question are
actually covered by multiple RTIs, then we still make "too many" calls to the
cli.
My gut feeling is that the multiple RTI case is extremely rare, and that this
RTI could be resolved either by updating the webrticli or the dblookup code.
--
Configure bugmail: http://bugs.grommit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
