Darcszilla - Darcs hooks on patch application
May 9th, 2006 tonyg
We’ve been using cvszilla here at LShift, and one feature we like that we want in Darcs is the ability for the version-control system to append notes (containing the log message) to a Bugzilla bug record every time a commit is accepted by our central repository.
I asked on the darcs-users mailing list, and the response I got indicated that the required functionality isn’t yet implemented. I’ve just pulled the unstable Darcs source tree. If I make any progress, you’ll hear it here first…
Entry Filed under: Tools
5 Comments Add your own
1. tonyg | May 9th, 2006 at 9:40 pm
Work is underway. There’s a patch for part of the required functionality attached to http://bugs.darcs.net/issue165.
2. matthew | May 10th, 2006 at 10:03 am
One of the things I like about monotone is that the revisions and transactions are kept in an SQL lite database on which you can perform standard SQL projections. This makes reimplementing something like cvszilla much easier. Also, monotone, using Lua has all kinds of hooks that can be scripted which would the adding-to-bugzilla bit easy too. Worth a solid look if you’ve not already committed to darcs - I’ve been using monotone for my entire individual project and it’s been rock solid and a pleasure to work with. Also worth a look are tools like monotone-viz which, with a bit of work, would be a very useful complement to cvszilla.
3. matthias | May 10th, 2006 at 4:30 pm
We haven’t. And yes, we have been looking at monotone.
4. matthew | May 10th, 2006 at 6:01 pm
How do you see such “distributed” SCM systems working in a centralised environment? Most of the SCM systems that I’ve looked at which make a big fuss about support for de-centralised working tend, at least at first glance, to not work too well for more typical centralised systems. Are you considering a central database (to use monotone’s terminology) that everyone synchronises with? If so, how do you prevent commits to local copies violating central policy (eg references to bug numbers etc)? At what stage do you add commit comments into bugzilla - when committed locally or when synchronized to the central database - if the former then references from bugzilla will point to the local copy rather than the central, but if the latter the typical behaviour will be that nothing appears in bugzilla until the entire bug is complete and the databases are synchronized.
5. matthias | May 10th, 2006 at 6:14 pm
One way, which is supported by darcs, is to make the policy part of the repository.
That’s generally ok.
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed