On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org> wrote:> I don't know the answer to this question, but I've attached an (old) > version of pybugz that I tweaked a little to work with LLVM bugzilla. You > can probably write such queries on top of this if you feel like figuring > out its API: >Thanks. Looks like most of the pages have some way to get them to spit out XML. Not quite as nice as a (well-documented) JSON REST API, but it's workable. I guess the REST API is a newer feature and our bugzilla is just old? -- Sean Silva> -- > > $ ./bugz get -n 1000 > > * Using http://llvm.org/bugs/ > > * Getting bug 1000 .. > > Title : Chris Is Buggy > > Assignee : tonic > > Reported : 2006-11-10 18:40:00 -0600 > > Updated : 2011-05-24 11:55:13 -0500 > > Status : RESOLVED > > Resolution : WONTFIX > > Severity : normal > > Priority : P > > Reporter : rspencer > > Version : trunk > > Platform : All > > OS : All > > Product : tools > > Component : analyze > > Keywords : regression > > CC : brukman+bugs > > CC : clattner > > CC : isanbard > > CC : llvmbugs > > CC : stuart > > DependsOn : 10000 > > Comments : 21 > > Attachments : 0 > > URL : http://llvm.org/bugs/show_bug.cgi?id=1000 > -- > > - Daniel > > > On Wed, Nov 6, 2013 at 10:59 PM, Sean Silva <silvas at purdue.edu> wrote: > >> Does anybody know if we have bugzilla's REST API enabled, and if so how >> to access it? <https://wiki.mozilla.org/Bugzilla:REST_API:Methods>. I >> tried e.g. http://llvm.org/bugs/bug/count but there doesn't seem to be >> anything there. >> >> I'd like to write a script that tracks various statistics e.g. how many >> bugs were filed in the last week, how many were closed, etc. and a REST API >> seems like the simplest way to automate (most of the methods corresponds >> directly to things in the Web UI, e.g. searches) >> >> -- Sean Silva >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131108/7c6546db/attachment.html>
On 08/11/2013 05:56, Sean Silva wrote:> > > > On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org > <mailto:daniel at zuster.org>> wrote: > > I don't know the answer to this question, but I've attached an > (old) version of pybugz that I tweaked a little to work with LLVM > bugzilla. You can probably write such queries on top of this if > you feel like figuring out its API: > > > > Thanks. Looks like most of the pages have some way to get them to spit > out XML. Not quite as nice as a (well-documented) JSON REST API, but > it's workable. > > I guess the REST API is a newer feature and our bugzilla is just old?Is there something I could contribute to help move this along, say an upgrade on the server? I'd like to cross-reference outstanding PRs against the codebase and most library/tool support out there today is set up for the more modern Bugzilla REST API. Alp.> > -- Sean Silva > > -- > > $ ./bugz get -n 1000 > > * Using http://llvm.org/bugs/ > > * Getting bug 1000 .. > > Title : Chris Is Buggy > > Assignee : tonic > > Reported : 2006-11-10 18:40:00 -0600 > > Updated : 2011-05-24 11:55:13 -0500 > > Status : RESOLVED > > Resolution : WONTFIX > > Severity : normal > > Priority : P > > Reporter : rspencer > > Version : trunk > > Platform : All > > OS : All > > Product : tools > > Component : analyze > > Keywords : regression > > CC : brukman+bugs > > CC : clattner > > CC : isanbard > > CC : llvmbugs > > CC : stuart > > DependsOn : 10000 > > Comments : 21 > > Attachments : 0 > > URL : http://llvm.org/bugs/show_bug.cgi?id=1000 > > -- > > - Daniel > > > On Wed, Nov 6, 2013 at 10:59 PM, Sean Silva <silvas at purdue.edu > <mailto:silvas at purdue.edu>> wrote: > > Does anybody know if we have bugzilla's REST API enabled, and > if so how to access it? > <https://wiki.mozilla.org/Bugzilla:REST_API:Methods>. I tried > e.g. http://llvm.org/bugs/bug/count but there doesn't seem to > be anything there. > > I'd like to write a script that tracks various statistics e.g. > how many bugs were filed in the last week, how many were > closed, etc. and a REST API seems like the simplest way to > automate (most of the methods corresponds directly to things > in the Web UI, e.g. searches) > > -- Sean Silva > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu> > http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-- http://www.nuanti.com the browser experts
On Tue, Dec 10, 2013 at 9:46 AM, Alp Toker <alp at nuanti.com> wrote:> > On 08/11/2013 05:56, Sean Silva wrote: > > >> >> >> On Thu, Nov 7, 2013 at 4:58 PM, Daniel Dunbar <daniel at zuster.org <mailto: >> daniel at zuster.org>> wrote: >> >> I don't know the answer to this question, but I've attached an >> (old) version of pybugz that I tweaked a little to work with LLVM >> bugzilla. You can probably write such queries on top of this if >> you feel like figuring out its API: >> >> >> >> Thanks. Looks like most of the pages have some way to get them to spit >> out XML. Not quite as nice as a (well-documented) JSON REST API, but it's >> workable. >> >> I guess the REST API is a newer feature and our bugzilla is just old? >> > > Is there something I could contribute to help move this along, say an > upgrade on the server? >This is something that I think everyone would appreciate. Our bugzilla is in a really calcified state. Breathing some vitality into it would be great. The thing is that I don't think that any of us have any experience with running/upgrading bugzilla; if you have some background in this and want to try your hand at it I think it's a no-brainer. If bugzilla has some sort of mirroring capability, I think that a natural first step would be to try to run a mirror with the target version (not on LLVM's servers (server? our web presence is pretty pathetic...)), make sure everyone is onboard with the upgrade (I don't expect any issues), then do the upgrade to llvm.org/bugs (and take down the mirror). -- Sean Silva> > I'd like to cross-reference outstanding PRs against the codebase and most > library/tool support out there today is set up for the more modern Bugzilla > REST API. > > Alp. > > > >> -- Sean Silva >> >> -- >> >> $ ./bugz get -n 1000 >> >> * Using http://llvm.org/bugs/ >> >> * Getting bug 1000 .. >> >> Title : Chris Is Buggy >> >> Assignee : tonic >> >> Reported : 2006-11-10 18:40:00 -0600 >> >> Updated : 2011-05-24 11:55:13 -0500 >> >> Status : RESOLVED >> >> Resolution : WONTFIX >> >> Severity : normal >> >> Priority : P >> >> Reporter : rspencer >> >> Version : trunk >> >> Platform : All >> >> OS : All >> >> Product : tools >> >> Component : analyze >> >> Keywords : regression >> >> CC : brukman+bugs >> >> CC : clattner >> >> CC : isanbard >> >> CC : llvmbugs >> >> CC : stuart >> >> DependsOn : 10000 >> >> Comments : 21 >> >> Attachments : 0 >> >> URL : http://llvm.org/bugs/show_bug.cgi?id=1000 >> >> -- >> >> - Daniel >> >> >> On Wed, Nov 6, 2013 at 10:59 PM, Sean Silva <silvas at purdue.edu >> <mailto:silvas at purdue.edu>> wrote: >> >> Does anybody know if we have bugzilla's REST API enabled, and >> if so how to access it? >> <https://wiki.mozilla.org/Bugzilla:REST_API:Methods>. I tried >> e.g. http://llvm.org/bugs/bug/count but there doesn't seem to >> be anything there. >> >> I'd like to write a script that tracks various statistics e.g. >> how many bugs were filed in the last week, how many were >> closed, etc. and a REST API seems like the simplest way to >> automate (most of the methods corresponds directly to things >> in the Web UI, e.g. searches) >> >> -- Sean Silva >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu <mailto:LLVMdev at cs.uiuc.edu> >> >> http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >> >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > -- > http://www.nuanti.com > the browser experts > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131212/983d6bd1/attachment.html>