~bzr-pqm/bzr/bzr.dev

2767.2.1 by Aaron Bentley
Add documentation for hooks
1
Using hooks
2977.1.1 by Ian Clatworthy
First cut at new look User Guide including chapters 1 and 2
2
===========
3
4
What is a hook?
5
---------------
2767.2.1 by Aaron Bentley
Add documentation for hooks
6
2767.2.2 by Aaron Bentley
Split hooks doc into guide and reference
7
One way to customize Bazaar's behaviour is with *hooks*.  Hooks allow you to
8
perform actions before or after certain Bazaar operations.  The operations
9
include ``commit``, ``push``, ``pull``, and ``uncommit``.
3786.1.1 by mernst at mit
This patch improves the User Guide's documentation of hooks.
10
For a complete list of hooks and their parameters, see `Hooks
11
<../user-reference/bzr_man.html#hooks>`_ in the User Reference.
12
13
Most hooks are run on the client, but a few are run on the server.  (Also
14
see the `bzr-push-and-update`_ plugin that handles one special case of
15
server-side operations.)
16
17
.. _bzr-push-and-update: https://launchpad.net/bzr-push-and-update/
2767.2.1 by Aaron Bentley
Add documentation for hooks
18
2977.1.1 by Ian Clatworthy
First cut at new look User Guide including chapters 1 and 2
19
Using hooks
20
-----------
21
3089.3.15 by Ian Clatworthy
fix some links
22
To use a hook, you should `write a plugin <#writing-a-plugin>`_.  Instead of
2767.2.1 by Aaron Bentley
Add documentation for hooks
23
creating a new command, this plugin will define and install the hook.  Here's
24
an example::
25
26
    from bzrlib import branch
27
28
2767.2.2 by Aaron Bentley
Split hooks doc into guide and reference
29
    def post_push_hook(push_result):
30
        print "The new revno is %d" % push_result.new_revno
2767.2.1 by Aaron Bentley
Add documentation for hooks
31
32
3408.5.1 by Ian Clatworthy
fix User Guide example
33
    branch.Branch.hooks.install_named_hook('post_push', post_push_hook,
3256.2.21 by Daniel Watkins
Updated docs.
34
                                     'My post_push hook')
2767.2.1 by Aaron Bentley
Add documentation for hooks
35
36
To use this example, create a file named ``push_hook.py``, and stick it in
37
``plugins`` subdirectory of your configuration directory.  (If you have never
38
installed any plugins, you may need to create the ``plugins`` directory).
39
2767.2.2 by Aaron Bentley
Split hooks doc into guide and reference
40
That's it!  The next time you push, it should show "The new revno is...".
41
Of course, hooks can be much more elaborate than this, because you have the
42
full power of Python at your disposal.  Now that you know how to use hooks,
43
what you do with them is up to you.
44
3786.1.1 by mernst at mit
This patch improves the User Guide's documentation of hooks.
45
The plugin code does two things.  First, it defines a function that will be
46
run after ``push`` completes.  (It could instead use an instance method or
47
a callable object.)  All push hooks take a single argument, the
48
``push_result``.
2977.1.1 by Ian Clatworthy
First cut at new look User Guide including chapters 1 and 2
49
3805.1.1 by Martin Pool
Merge and tweak hook documentation
50
Second, the plugin installs the hook.  The first argument ``'post_push'``
51
identifies where to install the hook.  The second argument is the hook
52
itself.  The third argument is a name ``'My post_push hook'``, which can be
3786.1.1 by mernst at mit
This patch improves the User Guide's documentation of hooks.
53
used in progress messages and error messages.
3254.2.11 by Daniel Watkins
Added some information to the user guide regarding 'bzr hooks'.
54
55
Debugging hooks
56
---------------
57
58
To get a list of installed hooks, use the hidden ``hooks`` command::
59
60
    bzr hooks