[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Commit to repository and send changes somewhere else

From: Greg Thomas <thomasgd_at_omc.bt.co.uk>
Date: 2005-09-26 12:45:49 CEST

On Mon, 26 Sep 2005 12:20:09 +0200, Ryan Schmidt
<subversion-2005@ryandesign.com> wrote:

>On Sep 26, 2005, at 10:22, Philip Radford wrote:
>> However when they commit their changes back to the repository I
>> need to be able to also copy the change to our development server
>> which is where apache is set to serve the files for testing purposes.
>It's a FAQ:
>Note that I would expect developers to generally check in only
>working code.

Depending on the scenario, one might expect developers to check in
module tested code, ready for a wider system test. In which case, the
post-commit hook could be written to only update the WWW site when a
tag is created, which would typically be after a system test schedule.


This post represents the views of the author and does
not necessarily accurately represent the views of BT.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 26 12:50:41 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.