![]() ![]() And ‘branches’ where we’ll a separate instance of our files where we can work on our new prototype functionality.Īt this point we can check out the contents of the repository (which doesn’t actually contain any files yet) on to our local machine. Tags to contain sets of files that have been tagged with a label relating to a specific ‘revision’ (more on this later). Trunk to contain the project files that are stable that we don’t want to interfere with. Folders to contain the different types of file collections. Now we have a repository with the required starting structure. So, after you’ve created the repository you should have something like this on your Visual SVN Server… This is what gives us and SVN the capability to manage multiple instances of the same code/files. ![]() Note that we’re creating a repository here with Trunk, Branches and Tags folders. Just make sure that on the ‘Repository Structure’ dialogue select the ‘Single-project repository option… Head back to the VisualSVN server app and select create new repository:įollow the prompts, calling the repository something creative like ‘repo2’. Lets prepare that new repository so that it’ll support a trunk, branches and tags. However, to support these capabilities we’ll need to prepare a new repository first. These concepts of Tagging and Branching are explained in detail below. TORTOISESVN DOES NOT COPY LOG WHEN BRANCH CODEThinking ahead though you will want, at some point in the future, to combine this new prototype code with your existing working code. What you need is a new copy of the files in your repository that you can make changes to without affecting the existing repository. However, you don’t want to contaminate your existing repository (with all the working code) with a new prototype code that won’t work for some time. Your team wants to work together and collaborate on this so you want to continue using SVN for this new work. You and your team think pulling together a prototype version for this functionality would be a great idea. They’ve been released into a production environment and nobody wants to risk changing anything just in case you break something.Īlong comes your end user who says wouldn’t it be great if we could add some functionality to support X, Y, and Z. Say you have a set of files in your repository that is working perfectly. So we can use SVN’s tagging feature and tag that same revision with the tag v1.2 Far easier to remember and in line with the version number we could be using when we release our software.īranching is one of the core features in SVN that allows us to work on a different instance of the files the files that are contained in the repository. So you’re likely to get to the point where you have a stable set of files that you know are in good shape and the SVN revision number might be r2343. In a reasonably sized project, over a year or two, it’s not long before those revision numbers get into the thousands or even tens of thousands. Branching gives us the capability to create a copy of the folders/files in our repository and have a different copy to work on – without fear of corrupting our main copy.Īs you’ve probably already grasped every time you commit a changed file to the repository SVN gives the repository a new, incremented by 1, revision number. Tags allow us to give a more human-friendly name to a specific revision of our folders/files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |