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

question on Subverison confguration

From: <Chidambarathanupillai_Nagaraj_at_emc.com>
Date: Tue, 20 Jul 2010 14:10:07 -0400

Hi,
 
I am new to any version control system.
I need to create an environment to test the below.
How do we create multiple repositries on the Sub version system?
How to tag the branch looping 20 times?
Can anyone help me on this.
 
Create a large NFS file system for the source control repository and connect it to the Subversion system referred to as Rep1.

Create a large NFS file system for a second source control repository and connect it to the Subversion system referred to as Rep2.

Loop the following 20 times to create a deep Subversion repository for Rep1 and Rep2:

Checkout an old version of the Linux source code (Kernel series 2.6.27.44) and check it into the Subversion system.

Tag the branch (27.N, where N is 1-20)

Checkout one of the newer version of the Linux source code (Kernel series 2.6.34) and check it into the Subversion system.

Tag the branch (34.N, where N is 1-20)

Test 1 - Checkout times

From a server connected to the Subversion server, time how long it takes to do 10 sequential mainline checkouts from Rep1. Note the completion times for each checkout. Repeat using Rep2.

Test 2 - Build times

From 5 different systems talking to the Subversion server, setup private kernel build areas using Rep1 and another build area using Rep2.

From each build server, do a checkout of the kernel source based on 27.N from Rep1 and build it. Checkout 34.N and build. Repeat this process 5 times. Record total times for the checkouts and builds.

Repeat the above process for Rep2 using the build areas based on private build areas.
 
Thanks and Regards,
Nagaraj Chidambarathanupillai
Received on 2010-07-20 20:21:15 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.