Hey List,
I am looking to do some tools for sending in review requests and updating them with revised versions via fedora-devshell. I'm also planning on putting in some bits to query BZ for review requests, download them, and test them in f-devshell too. There has been some talk about wanting to help integrate this into review-o-matic, so this is something that could probably make it easier to do reviews too.
In order to test this, i would need a way to send and read entries in RH's bugzilla. I'm about to look for libraries to do so, but before i can start development, i will need a test environment of course. (Unless everyone likes seeing bogus review requests from me.) How do i go about emulating the parts of BZ i need to test this?
Cheers, Yaakov
There is python-bugzilla, which is an API to the XMLRPC interface of bugzilla. There's a non-production RHBZ instance at https://partner-bugzilla.redhat.com too. Let me know if you have any more questions and sorry for the top post which I can't help :/
On 1/18/09, Yaakov Nemoy loupgaroublond@gmail.com wrote:
Hey List,
I am looking to do some tools for sending in review requests and updating them with revised versions via fedora-devshell. I'm also planning on putting in some bits to query BZ for review requests, download them, and test them in f-devshell too. There has been some talk about wanting to help integrate this into review-o-matic, so this is something that could probably make it easier to do reviews too.
In order to test this, i would need a way to send and read entries in RH's bugzilla. I'm about to look for libraries to do so, but before i can start development, i will need a test environment of course. (Unless everyone likes seeing bogus review requests from me.) How do i go about emulating the parts of BZ i need to test this?
Cheers, Yaakov
-- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
2009/1/19 Yaakov Nemoy loupgaroublond@gmail.com:
Hey List,
I am looking to do some tools for sending in review requests and updating them with revised versions via fedora-devshell. I'm also planning on putting in some bits to query BZ for review requests, download them, and test them in f-devshell too. There has been some talk about wanting to help integrate this into review-o-matic, so this is something that could probably make it easier to do reviews too.
We have already put in efforts and written something which includes most bits of what you have stated here, though that is still in **not usable** form. So, I would like you to collaborate with review-o-matic* effort. In case it is okay with you we can discuss in detail on review-o-matic* mailing list[1]?
* To be renamed soon. [1] https://fedorahosted.org/mailman/listinfo/review-o-matic
2009/1/19 Rakesh Pandit rakesh.pandit@gmail.com:
2009/1/19 Yaakov Nemoy loupgaroublond@gmail.com:
Hey List,
I am looking to do some tools for sending in review requests and updating them with revised versions via fedora-devshell. I'm also planning on putting in some bits to query BZ for review requests, download them, and test them in f-devshell too. There has been some talk about wanting to help integrate this into review-o-matic, so this is something that could probably make it easier to do reviews too.
We have already put in efforts and written something which includes most bits of what you have stated here, though that is still in **not usable** form. So, I would like you to collaborate with review-o-matic* effort. In case it is okay with you we can discuss in detail on review-o-matic* mailing list[1]?
If you have code to both submit new reviews, and pull information from reviews in process, i'll use that. I'm not picky how i get that information :)
There was a couple of requests at FudCon to integrate code to actually run an evaluation locally through review-o-matic. It was on my agenda, as in Whenever I Get Around To It (TM).
I am subscribed to that mailing list, i believe. I'll have a look through R-O-M soon.
-Yaakov
2009/1/20 Yaakov Nemoy loupgaroublond@gmail.com:
2009/1/19 Rakesh Pandit rakesh.pandit@gmail.com:
[..]
We have already put in efforts and written something which includes most bits of what you have stated here, though that is still in **not usable** form. So, I would like you to collaborate with review-o-matic* effort. In case it is okay with you we can discuss in detail on review-o-matic* mailing list[1]?
If you have code to both submit new reviews, and pull information from reviews in process, i'll use that. I'm not picky how i get that information :)
Yes, there is. If you look at arch diagram[1] feeder part does the feeding of information and reporter part does the reporting part. We started of with implementing the bare minimum workflow and have minimum implementation of class blocks except middle one (Applcation block) and that is why it is bit **non usable** collectively. But yes you can directly look at RomBugzillaFeeder[2] and RomBugzillaReporter[3] for corresponding bugzilla examples.
There was a couple of requests at FudCon to integrate code to actually run an evaluation locally through review-o-matic. It was on my agenda, as in Whenever I Get Around To It (TM).
I am subscribed to that mailing list, i believe. I'll have a look through R-O-M soon.
You are welcome. Lets continue the discussion there. I have a request with infrastructure about changing project details As soon as they are resolved, I will ping you :)
[1] https://fedorahosted.org/review-o-matic/wiki/arch_image [2] https://fedorahosted.org/review-o-matic/browser/RomBugzillaFeeder.py [3] https://fedorahosted.org/review-o-matic/browser/RomBugzillaReporter.py
On Mon, Jan 19, 2009 at 4:35 PM, Yaakov Nemoy loupgaroublond@gmail.com wrote:
If you have code to both submit new reviews, and pull information from reviews in process, i'll use that. I'm not picky how i get that information :)
I'd been holding off on mentioning this publicly (until earlier today, at least), but given the topic it seems apropos. I've been working on a replacement to my (venerable but aging) post-to-review script: reviewtool.
https://fedoraproject.org/wiki/ReviewTool
reviewtool aims to take some of the pain out of submitting/reviewing packages, though only the submitting side of the tool is usable at this point. It is _not_ a "Review-Oh-Matic", and doesn't do anything a packager / reviewer can't do on their own... It works with our standard infrastructure tools (bugzilla, koji and fedorapeople.org) to automate the routine bits that are common to every submission: searching for bugs, koji scratch builds, generating correctly formatted review/branch submissions, pushing the spec/srpm to a publicly accessible location, etc, etc.
It's still pretty rough -- especially on the documentation side -- but very usable for submitting tix and managing those tix to completion.
-Chris