Dne 10.10.2010 13:46, Andre Klapper napsal(a):
is there any guide available explaining how to add another Bugzilla
instance to bugzilla-triage-scripts?
I've grep'ed and read the code a bit but it's still unclear to me what I
have to do / what to create to get
bugzilla.whatever.com supported.
Steps welcome.
I guess, file me an issue in the tracker. If you want to do it yourself
search for name of some bugzilla or its domain (
gnome.org could be
good). When I did it here, I've got:
jakoubek:bugzilla-triage$ grep -ri
gnome\.org {data,jsons,lib,tests}/*
data/bugzillalabelAbbreviations.json: "bugzilla.gnome.org": "bgo",
data/bugzillalabelNames.json: "bugzilla.gnome.org": "GNOME
Desktop",
jsons/BugZappers_data-prototype.json: "bugzilla.gnome.org":"GNOME
Desktop"
jsons/BugZappers_data-prototype.json:
"https://bugzilla.gnome.org/show_bug.cgi?id=",
jsons/Config_data.json:
"https://bugzilla.gnome.org/show_bug.cgi.*"
jsons/Config_data.json: "bugzilla.gnome.org":[
jsons/Config_gnome.json: "comment":"Thanks for taking the
time to report this bug.\nWithout a stack trace from the crash it's very
hard to determine what caused it. Can you get us a stack trace? Please
see
http://live.gnome.org/GettingTraces for more information on how to
do so. Thanks in advance!",
jsons/Config_gnome.json: "comment":"Thanks for taking the
time to report this bug.\nThis bug report isn't very useful because it
doesn't describe the bug well. If you have time and can still reproduce
the bug, please read
https://bugzilla.gnome.org/bug-HOWTO.html and add a
more useful description to this bug.",
jsons/Config_gnome.json: "comment":"Thanks for taking the
time to report this bug.\nThis bug report isn't very useful because it
doesn't describe the bug well. If you have time and can still reproduce
the bug, please read
https://bugzilla.gnome.org/bug-HOWTO.html and add a
description of how to reproduce this bug.\nYou'll also need to add a
stack trace; please see
http://live.gnome.org/GettingTraces for more
information about how to do so.\nThanks in advance!",
jsons/Config_gnome.json: "comment":"Thanks for taking the
time to report this bug.\nUnfortunately, that stack trace is missing
some elements that will help a lot to solve the problem, so it will be
hard for the developers to fix that crash. Can you get us a stack trace
with debugging symbols? Please see
http://live.gnome.org/GettingTraces
for more information on how to do so. Thanks in advance!",
jsons/Config_gnome.json: "comment":"Thanks for taking the
time to report this bug.\nHowever, this application does not track its
bugs in the GNOME bugzilla. We kindly ask you to report the bug to the
application authors. For a selective list of other bug tracking systems
please consult
http://live.gnome.org/Bugsquad/TriageGuide/NonGnome. \nIf
the affected third party application has a bug tracking system you
should investigate whether a bug for the reported issue is already filed
in this system. If it has not been filed yet please do so. Also ensure
that both bug reports contain a link to each other.\nThanks in advance!",
jsons/Config_gnome.json:
"https://bugzilla.gnome.org/show_bug.cgi.*"
jsons/Config_gnome.json: "bugzilla.gnome.org":"all"
jsons/Config_gnome.json: "bugzilla.gnome.org":[
lib/bzpage.js: // to be generally much more stable (even with other
bugzillas, e.g.
b.gnome.org)
lib/bzpage.js: * Note that
bugzilla.gnome.org doesn't have mailto: url but
lib/bzpage.js: *
https://bugzilla.gnome.org/page.cgi?id=describeuser.html&login=mcepl%...
jakoubek:bugzilla-triage$
So, it should be good to walk through all those files, find out why
bugzilla.gnome.org is mentioned and add your particular instance. And
then it is just testing and fixing whatever bugs you find, or places
where we expected that "THINGS ARE DONE THIS WAY", although they don't
have to be.
Other way would be to file me an issue in the Tracker, and I would
eventually do something about it. The first method is certainly faster
(and I think it shouldn't take more than one evening hacking session).
But I would be curious anyway, so please file that ticket even though
you would fix it yourself.
Best,
Matěj