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

Remote access and continuous integration

From: rjk1408 <rohanjoseph_at_gmail.com>
Date: Thu, 10 Jul 2008 14:08:42 -0700 (PDT)

Hi all,

        I have been looking through posts for answers to my questions -
found many similar threads, but nothing yet that is nearly exact. My
apologies for any repetition.

1. I have a svn repository setup on a server that resides locally where I
work. This repository is currently being accessed through Apache.

2.I am developing a continuous integration system, whereby, the entire
process of merging and committing work to the repository will be automated
(tests need to be performed on a persons code before it can be checked in

3. I wish to have a program running on a remote server (possibly a daemon
process), 1000 miles away, that will, at 11 pm every night, checkout the
trunk of the repository I mentioned in step 1.

Question: How do I configure my repository such that

a. The daemon process on the remote server reads and writes from my
repository through the http protocol through apache AND

b. The developers working along with me, move to the file-system access
(file:///) method of accessing the local repository.

I have attached an image
[ http://www.nabble.com/file/p18391942/remote_access_to_repo.jpg
remote_access_to_repo.jpg ]

that describes this scenario. Kindly excuse the typo's in the drawing.(
There are 3 USER 1's - it should be USER 1, USER 2, USER 3).

Thank you.

View this message in context: http://www.nabble.com/Remote-access-and-continuous-integration-tp18391942p18391942.html
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-10 23:10:16 CEST

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.