How to setup SVN Subversion with SQL Navigator (148479)

How to setup SVN Subversion with SQL Navigator , Install, Check in and check out in SQL Navigator(SQL Nav)?

This is a quick “step-by-step” tutorial for setting up a Subversion server for testing purposes within SQL Nav.  Subversion is based on a client-server model, therefore both need to be installed to use it.  Both do not necessarily have to be on the same machine (unless doing a local server install), but both need to exist in order to use Subversion.  Both, the client and server installs can be found here: Subversion

For the purposes of testing, TortoiseSVN binaries for Windows will be used in this tutorial; however, one of the Linux, BSD, or Mac servers, and a Windows-based client can also be used. Subversion has three connectivity modes for its server component:  local, svn, and WebDav. 

For a local server, a Windows server and client (as all management is handled locally).  For svn and WebDav, the server component can exist on other platforms.  The “svn” mode uses a TCP connection (similar to telnet, ftp, ssh, etc) to access the Subversion server.  The “WebDav” mode uses an HTTP(s) connection to an internal, provided Apache web server. The configuration below is based on each of the server connectivity modes.

Local server connection Mode:

Download and install a windows server/client.

In this Tutorial, Setup-Subversion-1.8.8-1.msi for Server, and TortoiseSVN-1.7.4.22459-win32-svn-1.7.2.msi for Client.

On the Server navigate to a command prompt and type:

svnadmin create <repository path>  to create the repository. 

For example, svnadmin create c:\vcp\svn\Repository1

This command creates a number of subfolders in this repository.

Or Use the TortoiseSVN User Interface(UI) to create a repository.

Now, decide where the local working folder repository (or “Sandbox”) is to be located. 

For example,  c:\test\svn\<Repository name>, it can reside anywhere. 

"cd" to this directory (creating it, if necessary), and type the following:

svn co file://localhost/<path to repository>  to perform the initial check out of the repository. 

For example, svn co file://localhost/c:/vcp/svn/Repository1.

Or Using TortoiseSVN UI to create local work folder and check out:

Notice, Subversion uses URL convention, so all access to a server repository (including a local server) must be in this format.  This, however, only needs to be done once.  As soon as the Repository is checked out, a link is created between the two (local and server) repositories, so the local repository knows how to get back to the server repository.

Next, simply create a project in which to work.  To create a project, cd to the local working folder repository (created above) and type:

svn mkdir <Project Name>

svn commit –m “<message>”

For example:

svn mkdir Project1

svn commit –m “Initial Project”

In SQL Nav, enable Team Coding and select “Subversion (SVN)” as the 3^rd Party Version Control. 

When the Subversion login window appears, enter the server repository and local working directory.

Please note: No username or password is required for a local server connection. 

Now, set up the code control groups.

Team codingàcode | collection

After adding a group and including the db objects, one can check out and check in by right clicking or using the buttons.

SVN server connection Mode: 

Download and install a Subversion server and a windows Subversion command-line client. The TortoiseSVN client binaries work.  In the server installation wizard, the ability to define the default repository location for the server exists.

Open a new terminal (command prompt, if Windows) and type:

cd <Repository path>

svnadmin create <repository name>

to create the repository.  The default svnserve repository path is set when you install the svn server. 

For example: cd c:\svn_repository

svnadmin create Repository1

This command creates a number of subfolders in this repository.  Go into the “conf” folder of this Repository and edit the following files:

svnserve.conf:  Uncomment the “password-db” entry so it points to the passwd file.

passwd:  Add entries to the [users] section of the file, one for each user that will connect to the server.

Finally, make sure the svnserve daemon (or service) is running.  In Windows, this can be found by right-clicking on “My Computer”, selecting “Manage” and going to “Services and Applications à Services à svnserve.  In linux or BSD, edit the inetd.conf file located in the /etc folder.

Now, decide where the local Windows work repository (or “Sandbox”) is to be located. 

For example: c:\test\svn\<Repository name>.  It can reside anywhere.  “cd” to this directory (creating it, if necessary), and type the following:

svn --username <username> --password <password> co svn://<server>/<Repository name>

to perform the initial check out of the repository.  For example:

svn --username user1 --password user1pass co svn://localhost/Repository1 .

Notice, Subversion uses URL convention, so all access to a server repository must be in this format.  This, however, only needs to be done once.  As soon as the Repository is checked out, a link is created between the two (local and server) repositories, so the local repository knows how to get back to the server repository.

Next, simply create a project in which to work.  To create a project, cd to the local repository (created above) and type:

svn mkdir <Project Name>

svn --username user1 --password user1pass commit –m “<message>”

For example:

svn mkdir Project1

svn --username user1 --password user1pass commit –m “Initial Project”

Finally, in SQL Nav, enable Team Coding and select “Subversion (SVN)” as the 3^rd Party Version Control.  When the Subversion login window appears, enter your server repository and local working directory.

The initial login may fail, as the SVN options default to using the local server connectivity method.  To change this, go to Team Coding à Connection Settings à Provider Options. In this window, go to the “Server” tab, and select “SVN Server connection” and enter the server information.

Now, go back to the login screen and enter your username and password:

 or

Now, go back to the login screen and enter your username and password:

Finally, set up your code control groups.