Subversion (SVN) Basics for Version Control
Learn the fundamentals of Subversion (SVN) for effective version control in software development. Discover how SVN helps manage repositories, update working copies, commit changes, and execute essential commands. Dive into the world of version control with SVN at Kent State University.
Uploaded on | 1 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Subversion (svn) Basics Department of Computer Science Kent State University Prof. Jonathan I. Maletic
Version Control svn is a tool for version control of files Keeps a repository of what is under control at a central location Allows users to make local (aka working) copies of the repository on their machine or file system Saves each version a user commits Administrator sets up main repository.
Getting and Updating Checkout a repository. A local/working copy of a repository is created on a machine or file system. This links a given folder to the address of the repository. svn checkout address folder Update a local/working copy. The contents of the repository are copied to the local folder. This updates the local copy. svn update
Committing Changes Commit a change. Copy a local change to repository. This commits a change to the repository. This is a new version of the item under version control. It is numbered and the old version is saved. Need to commit: Modified files Added or removed files or folders svn commit file m Commit note
Other Essential Commands svn add add a file. A commit must be done after the add to commit it to the repository. svn delete delete a file, followed by a commit. svn log get all the commit messages. Use this to roll back to an earlier version.
Check Out Working Copy Machine: wasp Logged On Machine: svn svn Server svn co /svn/jmaletic/ cs23001 svn update cs23001/svn copy jmaletic/ cs23001/
Add & Commit Machine: wasp Logged On Machine: svn svn Server emacs Main.cpp svn add Main.cpp svn ci M Addedmain cs23001/svn jmaletic/ cs23001/ Main.cpp Main.cpp Copy
Commit a Change Machine: wasp Logged On Machine: svn svn Server touch Main.cpp svn ci M Modifiedmain cs23001/svn jmaletic/ cs23001/ Main.cpp Main.cpp Main.cpp V2 Main.cpp V2 Copy
Multiple Working Copies Machine: svn svn Server Machine: Labtop Logged On cs23001/svn svn co /svn/jmaletic/ cs23001 svn update jmaletic/ copy Main.cpp V2 cs23001/ Main.cpp V2 Machine: wasp cs23001/ Main.cpp V2
Commit a Change Machine: svn svn Server Machine: Labtop Logged On cs23001/svn touch Main.cpp svn ci m changeto main jmaletic/ Main.cpp V2 V3 Main.cpp cs23001/ Copy Main.cpp V2 V3 Main.cpp Machine: wasp cs23001/ Main.cpp V2
Update wasp Machine: svn svn Server Machine: wasp Logged On cs23001/svn svn update jmaletic/ copy Main.cpp V3 cs23001/ Main.cpp V2 V3 Main.cpp Machine: Laptop cs23001/ Main.cpp V3
Web Interface Machine: svn svn Server Browser https://svn.cs.kent.edu/courses/ cs23001/svn/jmaletic cs23001/svn jmaletic/ cs23001/ Main.cpp V3 Main.cpp V3
Rules to Live By (svn) Alwaysupdate before you start working Alwayscommit after changes Commit often after a major (or minor) change: Add a method Fix a bug Change a method
