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 |
4927.2.5
by Ian Clatworthy
improve links in hooks documentation |
11 |
<../user-reference/hooks-help.html>`_ in the User Reference. |
3786.1.1
by mernst at mit
This patch improves the User Guide's documentation of hooks. |
12 |
|
13 |
Most hooks are run on the client, but a few are run on the server. (Also |
|
4927.2.5
by Ian Clatworthy
improve links in hooks documentation |
14 |
see the `push-and-update plugin`_ that handles one special case of |
3786.1.1
by mernst at mit
This patch improves the User Guide's documentation of hooks. |
15 |
server-side operations.) |
16 |
||
4927.2.5
by Ian Clatworthy
improve links in hooks documentation |
17 |
.. _push-and-update plugin: http://doc.bazaar.canonical.com/plugins/en/push-and-update-plugin.html |
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 |
||
4927.2.5
by Ian Clatworthy
improve links in hooks documentation |
22 |
To use a hook, you should `write 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 |
|
4927.2.5
by Ian Clatworthy
improve links in hooks documentation |
36 |
.. _write a plugin: http://doc.bazaar.canonical.com/plugins/en/plugin-development.html |
37 |
||
2767.2.1
by Aaron Bentley
Add documentation for hooks |
38 |
To use this example, create a file named ``push_hook.py``, and stick it in |
39 |
``plugins`` subdirectory of your configuration directory. (If you have never |
|
40 |
installed any plugins, you may need to create the ``plugins`` directory). |
|
41 |
||
2767.2.2
by Aaron Bentley
Split hooks doc into guide and reference |
42 |
That's it! The next time you push, it should show "The new revno is...". |
43 |
Of course, hooks can be much more elaborate than this, because you have the |
|
44 |
full power of Python at your disposal. Now that you know how to use hooks, |
|
45 |
what you do with them is up to you. |
|
46 |
||
3786.1.1
by mernst at mit
This patch improves the User Guide's documentation of hooks. |
47 |
The plugin code does two things. First, it defines a function that will be |
48 |
run after ``push`` completes. (It could instead use an instance method or |
|
49 |
a callable object.) All push hooks take a single argument, the |
|
50 |
``push_result``. |
|
2977.1.1
by Ian Clatworthy
First cut at new look User Guide including chapters 1 and 2 |
51 |
|
3805.1.1
by Martin Pool
Merge and tweak hook documentation |
52 |
Second, the plugin installs the hook. The first argument ``'post_push'`` |
53 |
identifies where to install the hook. The second argument is the hook |
|
54 |
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. |
55 |
used in progress messages and error messages. |
3254.2.11
by Daniel Watkins
Added some information to the user guide regarding 'bzr hooks'. |
56 |
|
57 |
Debugging hooks |
|
58 |
--------------- |
|
59 |
||
60 |
To get a list of installed hooks, use the hidden ``hooks`` command:: |
|
61 |
||
62 |
bzr hooks |