Bugzilla Support

Asked by Deepinthekernel

On the page Bazaar vs Mercurial at http://bazaar-vcs.org/BzrVsHg it is stated "Bazaar has out of the box integration with Bugzilla, Trac and Launchpad's bug tracker."

I have scoured Google and Bazaar documentation for Bugzilla integration and can find little if any other reference to this. Is this a genuine feature and if so what does it mean and how do you configure it ?

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Deepinthekernel
Solved:
Last query:
Last reply:
Revision history for this message
Martin Pool (mbp) said :
#1

You can link commits to Bugzilla bugs through the --fixes option

http://doc.bazaar-vcs.org/bzr.dev/en/user-reference/bzr_man.html#bug-tracker-settings

I'm not sure off hand what configuration is needed on the Bugzilla side.

Revision history for this message
Deepinthekernel (mark-winder4) said :
#2

I have spent a day trying to make this work. I have manages to configure the client to accept the --fixes option. But what then?

No request is made to the supplied URL, whichever bug-tracker paradigm is used. Is this the expected behaviour?

Can these fixes entries be accessed in the hooks? Its not clear to me how or how you get information about the structure of the objects passed into the hooks.

For example doing a dir() on the push_result object reveals:

['__class__', '__delattr__', '__dict__', '__doc__', '__getattribute__', '__hash__', '__init__', '__int__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__str__', '__weakref__', '_show_tag_conficts', 'local_branch', 'master_branch', 'new_revid', 'new_revno', 'old_revid', 'old_revno', 'report', 'source_branch', 'tag_conflicts', 'target_branch']

and __getattribute__ could be the gateway into another world but its not at all clear how to access these.

Revision history for this message
Martin Pool (mbp) said :
#3

~jml says

"Take a look at 'bzr help bugs'. If it's not good enough, let me know and I'll patch it."

Revision history for this message
Deepinthekernel (mark-winder4) said :
#4

The problem I am having with this is what to do next, specifically:

"entry is included in the 'bugs' revision property" how do you get this information out in any useful format?

At the moment I am going to look at some code I have been sent and see if this clarifies matters. ...

Revision history for this message
Jim Hague (banburybill) said :
#5

This is puzzling me too. OK, so you get this rev property set with

http://bugzilla.my.org/bugzilla/show_bug.cgi?id=1150 fixed

Then what? There's absolutely no sign of any actual Bugzilla integration in the bzr tree that I can find.

Revision history for this message
Manfred Bergmann (mdbergmann) said :
#6

Where do I have to set the tracker URL (bugzilla_<tracker>_url).
Is this in some bzr config file?

Manfred

Revision history for this message
Marius Kruger (amanica) said :
#7

(@Manfred I think this should have been a new question)

In ~/.bazaar/bazaar.conf put eg:
bugzilla_squid_url = http://www.squid-cache.org/bugs
this would allow bzr commit --fixes squid:1234 to mark Squid’s bug 1234 as fixed.

please see the following for details:
http://doc.bazaar.canonical.com/bzr.2.2/en/user-reference/bugs-help.html
(to find the exact Bazaar configuration dir run bzr version)

Revision history for this message
Manfred Bergmann (mdbergmann) said :
#8

Yeah, thanks, I found it in the docs.

Revision history for this message
kelvin0 (david-v) said :
#9

I also got the commit --fixes configured, and am able to commit bug fixes.

The problem is, how do you get the bug information for a particular revision.

But I still haven't found how to extract bug fix 'metadata' for any particular revision I tried
bzr log ...
bzr version-info --custom ...

Nothing! Is there a way to extract the bug fix info, without coding an extension/hook?
This thread was promising, but the resolution of the issue nevers seems to be addressed ..

Thanks,