| bob2 | aquarius, with a hook | 01:24 |
|---|---|---|
| aquarius | bob2: I couldn't find anything about running hooks on the server -- client hooks I understand, but server hooks didn't seem to be documented anywhere I could find -- but that likely means I just didn't find it :) | 01:25 |
| === r0bby is now known as robbyoconnor | ||
| mgz | morning | 09:39 |
| jelmer | hey mgz :) | 09:50 |
| LarstiQ | aquarius: they work basically the same way as local hooks | 11:06 |
| LarstiQ | aquarius: they're just configured on the server | 11:06 |
| LarstiQ | aquarius: (also note separately there is bzr-upload which can be nice for deployments) | 11:07 |
| aquarius | LarstiQ: I'm not sure *how* to configure a hook on the server; perhaps I'm just stupid :( Hooks are configured in plugins; plugins go in my ~/.bazaar folder. The server's a server: it doesn't have a home directory. | 11:22 |
| LarstiQ | aquarius: it does :) | 11:23 |
| LarstiQ | aquarius: are you using bzr+ssh or something else? | 11:23 |
| aquarius | bzr+ssh, yep | 11:23 |
| LarstiQ | aquarius: then it sets up an ssh connection and runs the bzr on the other side, as the user you're logging in with | 11:23 |
| aquarius | right. So I can install the plugin which runs the hook in server:/home/myuserid/.bazaar but then it'll only run the plugin when *I* push to trunk. | 11:24 |
| aquarius | I would like the plugin to run when a new rev is pushed to trunk, regardless of who does it, without having to have every user on the server install the plugin. | 11:24 |
| aquarius | (and without having to do magic sshness to make everyone on teh server actually ssh in as some sort of "bazaar" user) | 11:25 |
| LarstiQ | aquarius: or you could install it in bzrlib/plugins/ for example, and (iirc), set the config in .bzr/branch/branch.conf | 11:25 |
| aquarius | aha, set the config in .bzr/branch/branch.conf, that sounds like the sort of thing I want. I didn't find any references to that at all, although I'm probably just looking in the wrong place! | 11:26 |
| * aquarius googles :) | 11:27 | |
| LarstiQ | iirc there are also inotify watchers, which saves you from having to create a new .bzr/branch/branch.conf for new branches | 11:28 |
| LarstiQ | of course, if you are in full control you could also handle it in the plugin | 11:29 |
| LarstiQ | aquarius: unfortunately things are a bit more complex than with say svn :/ | 11:29 |
| * LarstiQ back to math | 11:29 | |
| aquarius | LarstiQ: ah, I'm OK without the inotify stuff; what I specifically want to do is, when a new rev hits trunk, bzr export it into a folder (this is to deploy our staging server direct from trunk). I don't need to do that for many different branches. | 11:30 |
| aquarius | This looks like the right approach. Thanks! | 11:30 |
| === beuno_ is now known as beuno | ||
| === yofel_ is now known as yofel | ||
| === deryck is now known as deryck[lunch] | ||
| === deryck[lunch] is now known as deryck | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!