On 02/28/2012 02:47 PM, Platonides wrote:
I think there was an interest for making bugzilla
patches into gerrit
automatically.
That should make the need for a gerrit account much smaller.
That is Rusty Burchfield. I believe he was working on this a little bit
at the SF hackathon. He said in an email to me last week (he said it
was ok to forward):
Currently there is some basic code up on GitHub that
is capable of
grabbing patches from Bugzilla and testing to see if they apply on
trunk.
If you saw the post I made to wikitech a while back, that
functionality is basically the same. However, it is available as a
gem with fewer dependencies on this branch.
https://github.com/GICodeWarrior/patch-tester/tree/gemify
Once Git and Gerrit are operational, the code could be modified to
apply the patches to trunk, and push them up into Gerrit for review
and testing.
If you are interested in hacking on or taking over any of this stuff,
feel free.
He's referring to "[Wikitech-l] Patch backlog automation" from November,
I believe:
Basically I fetch pages with curb(libcurl) and pull
out what I need with
nokogiri(libxml2) and some css selectors. Then I take each patch and attempt an
exhaustive search (after trying the easy cases) to see if it will apply.
Mark says:
Ideally, I would like to have this integrated into a
Bugzilla (which
would mean Perl, probably) or Gerrit (which would mean Java or, maybe,
JRuby).
Given that we currently have about 130 patches awaiting review on
MediaWiki core, and about 60 for extensions that WMF deploys (some going
back years), I think it's going to make a big difference to surface
those and put them into the same dashboard that reviewers use to see all
the pending pull requests. So if Rusty or another contributor has time
to work on this, I think it would have a dramatic effect on our patch
backlog.
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation