Professional Documents
Culture Documents
Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
1/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 2/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 3/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
What?
Subversion maintains snapshots of the code repository. Allows many people to concurrently work on a codebase. Subversion is source control with a central repository. Usually integrates with a frontend: Trac
4/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Why?
Continuous incremental backup. Ability to recall older code. Distributed development. Various versions of a single project. Tracking bugs, timeline, goals and releases.
5/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Central Repository
6/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
How?
Developers checkout code from the repository to a local working-copy. After making edits, they commit changes. At any point, they can revert to an older version of the codebase. They update their local working copy frequently to keep up with changes.
7/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
8/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
A system to track changes in les. The code is initially imported into the repository. Then a special subversion-aware directory is checked-out. Developers commit and update. Subversion tracks the changesets and the commit-log.
9/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 10/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
checkout: Obtain a new working copy. import: Import code into repository initially. commit: Update repository with changes. update: Update working-copy with changes. Other commands: revert, move, copy, merge.
11/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 12/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
To be shown . . . For examples see slides 4977 in the presentation SVN SubVersioN here:
http://www.slideshare.net/slidesharechaos/svn-subversion
13/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 14/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
GUI Tools
TortoiseSVN in Windows Right-click a directory: get a context-menu with everything in there. Useful Integration with di and patch. Reasonably fast.
15/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 16/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Project Layout
trunk/ All constant development happens here. branches/ Special purpose development here. tags/ Releases are tagged for archiving.
17/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Outline
1 What, Why and How? 2 Subversion Commands 3 Demo: Command-line Tools 4 GUI Tools 5 Project Layout 6 Demo: Trac
Guy K. Kloss | Software Version Control using Subversion 18/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Web frontend to a Subversion repository. Shows the changesets and timeline. Has a bug tracker which integrates with the Subversion commit-log. Simple project management.
19/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Follow the branches, tags, trunk structure. All code should be in the repository! Update code at the start of every day. Only commit coherent changes. The central repository should always be consistent. No dependent stu! Branch as less as possible.
20/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
Questions?
G.Kloss@massey.ac.nz
21/22
What, Why and How? Subversion Commands Demo: Command-line Tools GUI Tools Project Layout Demo: Trac
References
Thanks to Vishnu Gopals presentation Basic SCM with Subversion & Trac Subversion Quick Reference Card
http://www.digilife.be/quickreferences/quickrefs.htm
22/22