SVN Handbook for Developers
The SVN Server can be accessed at http://svn1.euroblaze.de. This is the web front-end to view code and manage your account settings.
A username for your login and the associated email account will be emailed to you individually. You can thereafter request a password reset using the Password Reminder Form.
This login will allow access to:
- Web functionality at http://svn1.euroblaze.de
- Your account/profile management
- Web-views of code stored in the SVN repository
- SVN repository access to various projects assigned to you (for commit, update, checkout etc. operation)
Windows users may use the TortoiseSVN client available for free from http://tortoisesvn.tigris.org. Please ensure to read documentation and practice using this client as much as possible before using it on real repositories, since mistakes could in the worst case lead to erasion of full code-repositories.
Linux users will find the shell based svn clients immensly useful and powerful for the purpose of accessing the SVN-server. Please use man for obtaining first information.
As a developer, you will be using the SVN server almost on a daily basis, and even more so when you are commiting code that will be exposed to customers. A project's life-cycle in an SVN repository are as follows:
- At the very beginning of the project's life in the SVN-repository, the SVN Administrator performs an import of a project into a repository. This becomes the code-base upon which all future developments are based on.
- Developers checkout a copy of this code-base and create a local copy on their development machines. This copy, called the Working Copy (WC), is what developers use on a day-to-day basis. Developers develop on the WC.
- See also SVN Clients
It is important to bear in mind that SVN commits function at a directory level. This means we always provide full directory paths when commiting files to the repository (and never individual file names).