Tortoise SVN Instalation and Using

Download Installer

Download the compressed TortoiseSVN installer from their website.

Please choose the latest version available.

http://tortoisesvn.net/

Unzip and Launch Installer

Unzip the installer to the same (temporary) directory. The installer is typically

delivered as Windows Installer Package (.msi):

Install Process

Double-click this installer “TortoiseSVN-1.2.2.4295-svn-1.2.3.msi”.

The TortoiseSVN Installer will be initialized. Click “Next >” to continue:

Accept License Agreement

Accept the End-User License Agreement and click “Next >” to continue:

Customize Setup

Installation all features and use of the default installation folder is recommended.

Click “Next >” to continue:

Start the Installation

Click “Install” to continue:

Confirm Successful Installation

After a few moments, you should see that TortoiseSVN was installed. Click “Finish”

to complete the installation. Note: the change log will be displayed.

Restart Windows

Because TortoiseSVN is a Windows Explorer shell extension, you really do you

have to restart Windows. Click “Yes” to restart immediately,

or “No” if you must wait to re-boot:

“Check Out” Source Code Repository

You are now ready to download a local “working copy” of the source code repository.

Please note that “Check Out” has nothing to do with the “Locking” of files; it is a

command that will simply download the repository contents. Normally, you will

perform the “Check Out” command just once during the project (unless you change

workstations), the ensuing occasions you will need to do an “Update” of your “working copy”.

Launch Windows Explorer and locate the directory where you would like to store

your local working copy of source code. The Technical Team recommends that

you create a directory called “work_area” on your “C:” drive.

The path would be:

C:\work_area

Assuming you have restarted your workstation, you should see a new set of

commands available when you right-click in Windows Explorer. Locate your “work_area”

directory, right-click, and select the “SVN Checkout…” command:

Set Checkout Options

First, enter the URL of the Subversion repository, which should have the following format:

svn://yoursvnhost.client.com/repositoryname

Depending on the repository you wish to work on, select:

svn://mks-pla-disvprod/custom_repos – for MKS_CUSTOM

svn://mks-pla-disvprod/noetix_repos – for NOETIX

Please note that you must be connected to the same network that the SVN server

resides on in order to access the repository.

Next, enter the “Checkout directory”, or destination, for your local working copy.

The recommend location is to use the same name as the repository

you are checking out, for example:

C:\work_area\custom_repos

All other options can be left to their default values. Click “OK” to continue.

Verify Folder Creation (optional)

If, in the “Checkout directory” option, you entered a folder that does not exist,

you will be prompted with the following message. Click “Yes” to create the folder and continue:

Wait while project files are downloaded

TortoiseSVN will now download the entire project repository…

Verify Checkout was Successful

You should see a message about each directory and file that was added to your local work copy.

Click “OK” to continue:

Get to Work (Basic Tortoise Usage)!

You should now have a local copy of the entire project directory tree available on your workstation.

You can begin to work by adding files, editing files, moving/copying files, etc.

In this section we will talk about “commit”, “add” and “SVN Update”

“ADD”

To prevent mistakenly adding into the Subversion repository a file that you do not want versioned yet,

it is recommended that you do your work on your usual development directories in Windows,

and copy the files into your local working area only when you want your changes to be registered

and versioned. In the same line, if you want to work on a file that is already in the repository,

copy it to your development directory and place it back when you are done or want a new version generated.

Please, try using TextPad or a similar tool and avoid using Notepad, Wordpad or Word.

Let’s work on a little example:

1. Go to your local development area and create, using Textpad, a text file and name it using your
2. :
3. Copy your new file into the “training” folder in your “work_area”
4. 
   
5. Look into the training folder and you will notice that the new file has a question mark (?) on the left hand side,
6. which means that the file is not versioned. Right-click on your file and “TortoiseSVN” -> “Add”
7. 
   
8. Click “Ok” on the screen that appears showing that your file will be added. If you choose to add several files,
9. all of them will be listed in a box like the one shown below
10. 
    
11. If the task is successful, a screen will appear specifying that. Also, you will notice a few changes:

1. 1. The question mark in front of the file has been replaced by a plus (+) sign.
   2. The green icon in front of the training carpet has been changed by a red exclamation point.
   3. This means that the content of the folder has changed and that something has to be “committed”.
   4. Same red icon will has appeared in front of your “custom_repos” working copy.

IMPORTANT: Every time a file is “committed” (we will talk about this command in the next section) into the repository,

it gets moved into its corresponding directory in DEV1, be it $MKS_CUSTOM, noetix_install_dir or any other custom

area in DEV1. This also means that there will be no need to move the files to the development server via ‘ftp’.

“COMMIT”

It is now time to commit your work into the repository, whether because you added files, updated others or both.

Remember that, as we mentioned at the end of the “ADD” section above, every file that gets committed into the

repository will automatically be moved into its corresponding directory in $MKS_CUSTOM, noetix_install_dir or any

other project registered in the Subversion repository. For that, you have to be careful on what you commit,

and that is also another reason why it is recommended to work on a separate development area.

Now, let’s commit our previous example to the repository. This can be done in 3 ways:

a. Committing the whole project, which would send any non-committed change made in our local

working area, into the repository.

b. Committing the folder, with the same situation mentioned above but for the whole folder.

c. Committing only the file. Whenever a commit is issued a prompt appears in order to enter a log change.

This log change should be the CCD# followed, if possible by relevant information regarding the change,

for example: “CCD# 2009-01-01 – Training file added”. In view of that, this option (commit a file at a time)

is the one recommended for most cases.

Since we are going to choose the third option:

1. Right-click on your file in your working area and select “SVN Commit…”

1. Add a note to the log specifying the CCD#, like mentioned above, and any other relevant information.
2. Click “Ok” when you are done.

1. Type in your Subversion username and password provided and click on “Ok”.

1. If the commit is successful, you will see a screen like the one below, including your file with a green
2. check mark, as
3. well as the “training” and project folders. If there were other files elsewhere that are pending to
4. be committed,
5. the red exclamation point will keep showing in the corresponding folders.

1. And, as mentioned before, the file has been transferred into $MKS_CUSTOM in DEV1 automatically
2. when it was committed.

“SVN Update”

SVN Update will perform an update of your local work area. This action is recommended to be done at least at the

beginning of the day in order to have the latest version of the repository in our working area.

1. Go to the project name of you’re the working copy and right-click on it. Select “SVN Update”

1. You will get a screen with all the changes that have been performed to your working copy. Click “Ok”.

1. Go to the training folder in your local working area and you should see all the files that have been
2. created and placed into the repository by others who have done this same training

Congratulations

You have completed the basic Subversion and Tortoise training and are ready to start working on your own.

However, as this is a basic training, please do familiarize yourself by reading the TortoiseSVN User’s Guide

Chapter 5. This document is available from the Tortoise website as well as the Tortoise Help.

In addition, you are advised to become familiar with TortoiseMerge, a diff/merge tool built into TortoiseSVN.