Community
Participate
Working Groups
If we want to have Hudson integrated w/ Bugzilla (bug 253281), we need to enable XMLRPC [1]. [1]http://wiki.hudson-ci.org/display/HUDSON/Bugzilla+Plugin?focusedCommentId=36601879#comment-36601879 Is that possible? If so, the next steps to verify the integration works are to enable the plugin [2], restart Hudson, configure the plugin, and then see if numbers appear in changelogs [3, 4]. [2]https://build.eclipse.org/hudson/pluginManager/installed [3]https://build.eclipse.org/hudson/job/cbi-gef-3.5.x-nightly/3/changes [4]https://build.eclipse.org/hudson/job/cbi-gef-3.5.x-nightly/4/changes
I want to get Bugzilla 3.2 installed before considering this.
+1 for accessing Bugzilla WebServices via XML-RPC.
Now that Bugzilla is updated (thanks!), can we explore the idea of Hudson-Bugzilla integration w/ XMLRPC?
Yes, yes we can. I haven't closed this as WONTFIX, did i?
(In reply to comment #4) > Yes, yes we can. I haven't closed this as WONTFIX, did i? No, but you did say "I want to get Bugzilla 3.2 installed before considering this." So, consider this a reminder to have the request bubble back up to the foreground (dormant since March) for consideration. Of course getting Bugzilla back to the speed it was before the upgrade should *ahem* /eclipse/ this feature request priority-wise. :)
(In reply to comment #5) > So, consider this a reminder to have the request bubble back up to the > foreground (dormant since March) for consideration. You're tough. I wouldn't consider reminding someone unless I am under the impression that they forgot -- especially when I am able to tell them they have a higher priority. :) Isn't this like posting a reminder on 6000 bugs the day of June 25?
> Of course getting Bugzilla back to the speed it was before the upgrade should > *ahem* /eclipse/ this feature request priority-wise. :) If you insist... Making this depend on bug 283034...
After reading the docs(http://www.bugzilla.org/docs/3.4/en/html/api/) I have the following concerns: 1) The majority of functions are marked as 'experimental','unstable' or 'deprecated'. 2) It offers an opportunity to spam people via offer_account_by_email. 3) The User::get() method could allow for user details leakage. I'm sure there are ways to solve #2 and #3, but frankly #1 scares me. The added load that this can generate also needs to be considered. We just don't have the cycles to make this happen and address these concerns. I'd prefer to mark this 'later', but it's going to be 'wontfix'. -M.
Hi Denis, As part of the project we have the aim to provide a plug-in that is able to create an eclipse account from the workbench. We stumbled upon the fact that the RPC api is closed and then found this bug. Since this is already two years ago, we wonder if you have some more faith in the stability of the RPC api. We also noticed that mylyn has some special access to the bugzilla thru this link: http://mylyn.eclipse.org/bugs40/xmlrpc.cgi but that will not allow us to create accounts. Is there some API that we can use to create an Eclipse account? It just seems so nice to embed account creation inside eclipse.
(In reply to comment #9) > We also noticed that mylyn has some special access to the bugzilla thru this > link: > > http://mylyn.eclipse.org/bugs40/xmlrpc.cgi > Scratch that. That points to a test bugzilla
I would also like to ask you to re-consider this decision. Since years, I try every now and then to get some usable bug stats for our project, but no avail. Bugzilla itself offers some stats, but there are not useful as they do not show progress over time. I made a couple of approaches to get hold of some bug stats, including screen-scraping the history HTML files etc, but that's of course horrible. My latest try was to use Mylyn's APIs, but also Mylyn cannot retrieve any bug stats without XMLRCP: org.eclipse.core.runtime.CoreException: XMLRPC is not available at org.eclipse.mylyn.internal.bugzilla.core.BugzillaClient.getBugHistory(BugzillaClient.java:2374) at org.eclipse.mylyn.internal.bugzilla.core.BugzillaRepositoryConnector.getTaskHistory(BugzillaRepositoryConnector.java:1083) ... Bugzilla contains important data for all Eclipse projects and I think these data should be accessible. The Bugzilla 4.0 API doesn't seem to regard any methods as experimental or unstable anymore.
Wow. I'm a new committer (on Paho) and I've just started to try setting up some mobile clients to better manage my Bugzilla interactions... but of course, they would like the XML-RPC interface to be enabled. What's the current status on this - can we get some attention to this idea again?
*bump* now that the DC migration is done, how about opening up XML-RPC access for Bugzilla?
(In reply to comment #13) > *bump* > > now that the DC migration is done, how about opening up XML-RPC access for > Bugzilla? +1
Bugzilla is one of our core services, where if it gets too slow, people get seriously angry. Thanks for being patient -- we'll investigate this.
Understand the core nature of the service. I had a trawl of Bugzilla release notes etc and can't see mention of xmlrpc/jsonrpc causing performance issues. Would be great to be able to hook external tools in for management and so on.
> I had a trawl of Bugzilla release > notes etc and can't see mention of xmlrpc/jsonrpc causing performance > issues. The feature itself is not the issue -- it's exposing it to a world of people (and devices) who already have no mercy for our poor little Bugzilla.
I've enabled xmlrpc.cgi on Bugzilla: https://bugs.eclipse.org/bugs/xmlrpc.cgi Let me know how it works out.
Working great so far for the Eclipse Lyo OSLC adapter for Bugzilla.
Great, I'll close this as fixed then. cc'ing Steffen in case this is something the Mylyn crew is interested in.
Thanks.
Yep, working for me with iBzilla - fantastic! Thanks.
Thanks, now you can enable this in Mylyn. In "Properties for Task Repository" in the "Additional Settings" enable "Use xmlrpc.cgi" This activate the following features: a) use the Valid Transitions from editworkflow.cgi b) the default "Target Milestone" is now in the configuration and set for new bugs c) for an selected Task in the Tasklist you can get the History in the History view with "Navigate" -> "Show in ..." -> "History"
