Forcing mandatory checks on repositories

[Robert Collins]

On Wed, 2009-02-25 at 02:25 +0100, Frits Jalvingh wrote:
> Hello all,

> Since we use a set of main repositories on a server I then looked at capturing 
> a push on the server before it was committed into the server copy of the 
> repo; if I could "see" the new version of the repo before it was written I 
> might be able to do the check then. But this seems to be impossible - the 
> only hook I found is a post-push one. Given the nature of push this seems 
> hard anyway.

The Branch hook 'pre_change_branch_tip' will let you enforce any policy
you like on change to a branch. Create a plugin and install it on your
server; as long as the clients are using bzr 1.6 or above this hook will
fire on every push (or commit-to-the-branch). You should also disable
(or just don't tell your devs) the sftp:// protocol (because with dumb
protocols server side hooks are not triggered).

> Does anyone know of a way to ensure that checks are done, preferably at commit 
> time? I will look at things like PQM but would prefer to use bazaar only.

PQM is part of the bzr family :) But its not needed here.

Cheers,
Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090225/d29187d4/attachment.pgp