Open GoogleCodeExporter opened 9 years ago
part of this might be
<http://gerrit.googlecode.com/svn/documentation/2.1/config-gerrit.html#commentli
nk>
Original comment by desoxyrebonukleinsaure@gmail.com
on 28 May 2013 at 2:38
Just to update here, dependencies to build its-bugzilla for gerrit bugzilla
integration can be fetched from
http://central.maven.org/maven2/com/google/gerrit/.
Add this repo to your settings.xml.
Original comment by khanna7r...@gmail.com
on 21 Aug 2014 at 10:14
But Still after integration its-bugzilla plugin and its configuration , after
pushing the commits to gerrit not reflecting on gerrit.
Original comment by khanna7r...@gmail.com
on 26 Aug 2014 at 8:24
Hi Khanna7r What version of bugzilla are you running?
I believe that bugzilla 4.4.4+ wants tokens passed for XMLRPC instead of
sessions, and that its-bugzilla -> posting to bugzilla is currently broken.
Wikimedia is using this plugin and they created a patch against and older
version of the plugin, but their gerrit only shows a binary diff and I cant
tell what they did to fix it. I am also interested in getting this working.
Relevant patch: https://gerrit.wikimedia.org/r/#/c/133732/
Original comment by act...@aricgardner.com
on 5 Sep 2014 at 3:51
One more bump, here is the relevant bug on wikimedia's tracker.
https://bugzilla.wikimedia.org/show_bug.cgi?id=65370
Original comment by act...@aricgardner.com
on 5 Sep 2014 at 6:26
I think compatibility with Bugzilla 4.4.4 can be fixed by bumping the
J2Bugzilla requirement from 2.2 to 2.2.1. See issue 2902 for details.
Original comment by gerald.c...@gmail.com
on 28 Sep 2014 at 8:21
Any news about this problem? I'm trying to use the its-bugzilla plugin (commit
a909bfc836b1a97a7afcd45d085bda6ef4ec6371) on gerrit v2.9.4 with bugzilla v4.4.6
but i'm unable to post any update to bugzilla.
Neverthless the plugin say that it has successfully connect to the bugzilla
server and after that it doesn't give any error.
I'm not sure if it's the same problem of this issue.
Original comment by fabio.po...@gmail.com
on 20 Jan 2015 at 4:01
Original issue reported on code.google.com by
DamienVa...@gmail.com
on 17 Dec 2010 at 2:44