plugin to update the working tree after push to remote machine?

[John Arbash Meinel]

Alexander Belchenko wrote:
> Is there is a plugin or method to easily update of working tree after
> push to remote machine via sftp? I remember that bzr does not update
> because it potentially very slow operation.
> 
> I run in the case when I need often push my changes to testing machine
> and build new version and run this for testing. I soometimes forgot to
> do 'bzr update' on pushed location.
> 
> May be there is a way to automatize this? My co-worker is newbie in bzr
> and this moment (update after push) he time to time forget.
> 
> -- 
> Alexander
> 

There is 'bzr rpush' provided by my rsync plugin:
https://launchpad.net/products/bzr-rsync

Which tries hard to be safe even when using a shared repository. It may
be slightly out of date with the current bzr.dev. But it should be
fairly easy to bring up to date.

There is also 'rspush' in the bzrtools package. But IIRC it always
spawns rsync, which means it may do the wrong thing if the remote
location is a shared repository.

(rpush checks, and if the remote is shared, it does a regular push, and
then rsync to update the working tree).

It may be possible to update remote working files through a Transport
and the TreeTransform interface, but this hasn't ever been worked through.

John
=:->

PS> rpush also defaults to only rsyncing files that have been updated,
though you can pass a flag to update everything. This is at least an
attempt to avoid stepping on remote modified files.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061020/8a817d00/attachment.pgp