389875 - Bugzilla/Mercurial integration

Status: RESOLVED WONTFIX

(Bugzilla :: Attachments & Requests, enhancement)

Description

[Daniel Brooks [:db48x]]

I'm probably not the first to think of this, but I think it'd be cool if Mercurial repositories were integrated into Bugzilla.

The way I imagine it working would be a single repository per bug, cloned from one of the master repositories (which one could be determined by the product the bug is filed in). This repository need not be created for every bug. Just giving the user an opportunity to create one, similar to the way they can create an attachment at any time, is enough. The user or users interested in working on that bug could use this repository as a shared branch, pushing the changes to the new repository via https instead of ssh, and could at any time use a simplified interface to create a new attachment containing all of the revisions in that repository not present in the master (using 'hg bundle', or the equivalent from the python libraries).

Even further automation is possible. Once a particular bundle is properly reviewed, Bugzilla could automate the process of pushing the changes into the master repository.

Cloned repos can be fairly cheap if you can clone a repository on the same disk, just a few megs a piece. They'll then get bigger as each file that is changed removes a hard link. On the other hand, I believe that's larger than the largest attachment you can currently create. Luckily disks keep getting larger, and only the differences ever need be transferred over the network.

Comment 1

[Reed Loden [:reed]]

This sounds way overboard, and I don't think it's something worthwhile. When I said Bugzilla / Hg integration, I meant the same types of things we do for CVS now (extra context with patches, etc.).

Comment 2

[Daniel Brooks [:db48x]]

Actually, I had the idea before I read your comment in the other bug, but regardless, I do know it's a bit of a stretch. In any case, I doubt it would be part of the main bugzilla distribution, but instead would be installed separately. Basically though, once the dependent bugs are fixed, this is largely just a matter of some changes to the templates to add some buttons. There's no reason the repositories created in this manner need to be on the same server as bugzilla or anything.

Comment 3

[Frédéric Buclin]

This is not something I want to see implemented. You can implement this as a separate tool (plugin?), if you want to.