Re: [etch-users] Clustered etch server

[Pat O'B. <obr...@gm...>]

> We have our 6 etch servers independently pulling from subversion once an hour using the repo_update script included in the distribution.
>
> It works fine for normal distribution, but is somewhat suboptimal when you want to push something out in a hurry because you have to manually go to each server and run repo_update.
>
> It also means that there's no quick way to deploy the killswitch (https://sourceforge.net/apps/trac/etch/wiki/ControlledDeployment).  In my previous job I set up a separate once a minute cronjob to just update the killswitch so that at least that file was synced quickly without thrashing the subversion servers too much.
>
> So I'm also curious if there are any ideas out there about how to improve this.  It seems like there should be a better approach, but it isn't something I've spent much time pondering.
>
> Jason

We just have a cronjob that runs every five minutes on both servers
which updates trunk from SVN rather than updating it manually or
waiting an hour if we have to quickly push a change.

-pat