![]() ![]() NOTE: If you’ve got some cash, I highly recommend you donate to the TortoiseSVN project. You never know when they’ll come in handy (though I don’t intend to refer to them in this series).Īfter this, the app installs. Run the installer, accept the license agreement, and select the options for install.ĭuring this time, I usually right-click command line client tools and install it by choosing will be installed on local hard drive. Installing Tortoise is about as standard as it gets. You can download the 32-bit version or 64-bit version from their downloads page. ![]() The latest version as of this writing is 1.7.6. TortoiseSVN is pretty much the de-facto standard for Subversion clients on Windows. It’s the style that I believe I’ll adopt going forward, though don’t hold me to it. This is the general flavor that I’ve picked up in some places, including an excellent Pluralsight Continuous Integration Course by James Kovacs. NOTE: Before I begin, I should mention that while I will speak about them authoritatively, the methods for laying out repository structures are by no means set in stone, and are in fact debated quite vigorously at times in the tech community. Welcome back! Now that we have a TLS-encrypted Apache setup with SVN, we’re going to take a look at creating the repository layout. For more information and additional series links, check out the introductory post. This is part of a larger series in building a proper build process. ![]() Building a Build Process: TortoiseSVN Client Connection and Repository Layout ![]()
0 Comments
Leave a Reply. |