some newbie questions

[Sabin Iacob]

Erik wrote:
> Hi All, 
>
> What I noticed however, is that the files on the server don't change. The 
> -changes- we commit are stored (in the bazaar repository on the server I 
> guess), but the files on the server aren't updated, until I start a 
> command prompt on the server and do a "bzr update" there. This is favorable so 
> that our testers can simply take a look at the central server to see the 
> current situation. Is there a way to automate this? Do I need a hook for this,
>  or is there an easier way to have the files on the server update as soon as 
> someone commits from their respective checkout?
>   

that would be very helpful, indeed; I once attempted to solve the issue
by having a local post-commit hook that ssh-ed into the machine and ran
things (I wanted to automate bug commenting/closing in trac); I know
there have been plans for server-side hooks for a while, but I have no
idea what's the current status.

> Furthermore, I'm wondering if there is a functionality in bazaar that lets me 
> revert all files to a previous revision, just to test, and then lets me 
> change back to the latest point again. I would like to see sometimes how a 
> certain revision of the site used to work at that point. What commands should 
> I use there?
>   

bzr revert -r whatever
#test, test
bzr revert
#back to tip

> Third question is if it is possible to push a specific bugfix to different 
> trees. For example, we have a DEV a TEST and a LIVE environment. If we have a 
> critical bugfix for the live environment, can I just fix it on the DEV 
> environment and then push only this bugfix to test and live aswell? (in effect 
> skipping some other revisions that will be released later)?
>   

generally, the approach used in distributed version control is: identify
when the bug appeared, branch that revision, fix bug, merge into prod,
testing, devel, etc... I don't know how this fits into your workflow
(you seem to be using bzr as a drop-in replacement for svn).