Introduction to Version Control
Download as ODP, PPTX3 likes14,516 views
Version control is a method for centrally storing files and keeping a record of changes made by developers. It allows tracking who made what changes and when. This allows developers to back up their work, track different versions of files, merge changes from multiple developers, and recover old versions if needed. Centralized version control systems like Subversion store all files in a central repository that developers check files out from and check changes back into. Subversion allows viewing changes between versions, rolling back changes, and recovering old project versions with a single version number across all files.
More Related Content
Similar to Introduction to Version Control(20)
![From Curiosity to ROI — Cost-Benefit Analysis of Agentic Automation [3/6]](https://cdn.slidesharecdn.com/ss_thumbnails/session-3-250903141006-a3917e1a-thumbnail.jpg?width=560&fit=bounds)
Introduction to Version Control
- 1. Version Control Introduction/ Taster Use on-line resources, books or colleagues for more info Solution Perspective Media
- 2. Version Control Whatis it A method for centrally storing files Keeping a record of changes Who did what, when in the system Covering yourself when things inevitably go wrong
- 3. Version Control: Why?Individual Back-up methodology Increments – know which version is live Point in time marking aka. Tagging Branching – release versions maintained & main development can continue Change history – when features were added or amended Team As Individual plus: Allow multiple developers (in remote locations) to work on same code base Merge changes across same files – handle collisions Answer who did what – blame / praise
- 4.
- 5.
- 6. Version Control: TypesCVS – Concurrent Version System http://www.nongnu.org/cvs/ SVN – Subversion http://subversion.tigris.org/ Git* - http://git.or.cz/ Bazaar* - http://bazaar-vcs.org/ Mercurial* - http://www.selenic.com/mercurial/ Monotone* - http://www.monotone.ca/ VSS – Visual Source Safe – Microsoft visual tool * Distributed version control
- 7. Subversion Code centralisedin a repository Check out a working copy into a development area on local machine Make changes, test etc. Changes committed back to the central repository – usually with a useful comment Each work session an update is performed to get changes from other team members
- 8. Subversion Change log– who, when, what Check for differences between current version and any version in repository Create and apply patches between tags, branches and trunk Recover old versions of files, roll-back when it goes wrong Recover old versions of project – single version number for all files (unlike e.g. CVS)
- 9. Subversion Clients SVNcommand-line tool HTTP (WebDav) SVN+SSH Dedicated client tools for all major platforms Plug-ins for IDEs e.g. Zend Studio, Eclipse Automatic integration as a network drive (user doesn't need to know it's a version control system)
- 10. Subversion Resources Documentation,links to clients etc. at http://subversion.tigris.org/ Read Bean Book (Open Source) http://svnbook.red-bean.com/ Pragmatic Version Control Using Subversion – Mike Mason, Pragmatic Bookshelf Version Control with Subversion – Collins-Sussman, O'Reilly (Turtles)