| Summary: | tdesdk: Update kbugbuster to function with Trinity bugzilla | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | tdesdk | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | bugwatch, darrella, krisgamrat, mutantturkey, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | All | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: | Patch to fix branding, default server, and update server list. | ||
|
Description
Darrell
2012-01-19 22:58:50 CST
kbugbuster does nominally function with the Trinity bugzilla. * kbugbuster recognizes and connects to the Trinity bugzilla URL. * I can search the Trinity bugzilla by bug number. * After editing the server information with a login name and password, I can list the bugs written by me. Problems: * The kbugbuster default server is incorrect (originally bug report 1107). * Comments are viewable by bug number, but otherwise kbugbuster doesn't correctly parse the XML anywhere else. All other columns list as "Unknown." If these bugs were fixed then kbugbuster would improve dramatically as a bug tracking viewer. Unknown: * I have not tried to post changes or comments to a bug report. As I can list bugs written by me after adding my login name and password, I presume posting at least some changes are possible, but I prefer waiting until the above problems are resolved before moving to that next step. * I don't know what additional parsing support is needed for the various different releases of bugzilla. * I don't know whether there is a way to have kbugbuster automatically refresh its cache with each new start. *** Bug 1107 has been marked as a duplicate of this bug. *** Created attachment 785 [details]
Patch to fix branding, default server, and update server list.
This patch should be back portable to 3.5.13 SRU.
The next step is to figure out why the XML list is not parsing correctly, resulting in all text to be rendered as "Unknown." I'll tinker some more but I need help from a code expert.
I tried the patch v3.5.13-cord. The behavior is the same as you describe it. I looked at the source code KBugBuster to see what url is used to get information from bugzilla. For example, for a list of products is used: http://bugs.pearsoncomputing.net/xml.cgi?data=versiontable But, as I soon discovered, bugzilla 3.x not use xml.cgi, but XMLRPC or JSONRPC service - see: http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService.html This would mean either rewrite communication with a server in KBugBuster or on the server to create a custom implementation of xml.cgi. Overwriting communication with the server should probably add to KBugBuster general support for newer versions of bugzilla. From this perspective, therefore, it appears advantageous way. Ignoring the remainder of problems described here, are you saying the patch works in 3.5.13? If yes, then we should push the patch. Not a huge gain but at least the default server gets fixed. (Odpověď na komentář #6)
> Ignoring the remainder of problems described here, are you saying the patch
> works in 3.5.13? If yes, then we should push the patch. Not a huge gain but at
> least the default server gets fixed.
Yes, in v3.5.13-sru patch is working properly.
You can push it.
Possibly look at the KDE4 kbugbuster code to see how those people handle more recent bugzillas? Patch pushed to GIT in commit 8d38062c. I looked to KDE4. Solved so that the development of KBugBuster was stopped. When we implement a new communication with the server, we will be better! I think this has been pushed - should we close this report? (Odpověď na komentář #11)
> I think this has been pushed - should we close this report?
Issue left open because KBugBuster with Trinity Bugzilla still does not work.
kbugbuster needs more work. I suspect most of the repairs will be straightforward to an experienced coder. Mostly fixing XML parsing and some layout formatting. As nice as Deskzilla might seem, most people want to browse the bug tracker and perform queries with a native app. We have an app that can provide that service, is 98% functional, but needs attention. |