Post Commit Update

[Marius Boitor]

Thanks for all these.

The idea is that I am in search for an idea or more ideas that can do the
trick and I can rely on.
I've got my own approach but I don't know if it's the best approach.

I was thinking to use as John said hooks or at least this is what I've used
with SVN in different places.

Now is time for Bazaar because I have a blank sheet.This is the reason why I
wanted to know if there is a better approach than hooks and if any how
reliable is that approach.

Again, thank you very much for all.

Marius

On Wed, Sep 29, 2010 at 4:10 AM, Michael Andronov <
michael_andronov at sd-kyber.com> wrote:

> As John mentioned, there are 2 ways to access the bzr repository.
> In my case, I was not able to control the way people preferred to
> access the repositories.
> So, I had to assume that people would access the repository directly.
>
> I found the solution by monitoring the .bzr/repository/lock by inotify
> program.
>
> So, the script is maintained by cron, and the main part of it:
> "
> ...
> while /usr/local/bin/inotifywait -e delete  $srcR/.bzr/repository/lock
> | grep 'DELETE,ISDIR releasing' &> /dev/null; do
> #   the actual work will be done...
> su $bzrUser -c "$wrkDir/bzrPostCommit.py $cmdL "
> done
> ...
> "
> bzrUser -- the user, on which account the bzrPostCommit.sh will run;
> cmdL     -- inline parameters, if any;
> $wrkDit/bzrPostCommit.py -- the path to & the post Commit script itself...
> see 'man inotify' for details on inotify. (OSX has similar service via
> launchd)
>
> I'm not saying that the above is a perfect solution.
> But depending on what your goal is, the above may do the trick for
> your project too.
>
> Michael.
>



-- 
With respect,
Marius Boitor

Website: http://www.devessence.com
LinkedIn Profile: http://www.linkedin.com/in/mariusboitor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20100929/d17025a4/attachment.htm