Skip to main content

Configuration Management: Subversion (SVN)

Configuration Management
Subversion (SVN)
  • Show the following:

    Annotations
    Resources
  • Adjust appearance:

    Font
    Font style
    Color Scheme
    Light
    Dark
    Annotation contrast
    Low
    High
    Margins
  • Search within:
    • Notifications
    • Privacy
  • Project HomeTools and Techniques in Software Engineering
  • Projects
  • Learn more about Manifold

Notes

table of contents
  1. Introduction to Confirmation Mangement
  2. Tools
  3. Revision Control
    1. Subversion (SVN)
    2. Git
  4. Release Management
  5. Bibliography

Subversion: centralized version control

Subversion is a general version control system that manages files and directories, and the changes made to them. Any collection of files. It does not offer other features that come with configuration management systems such as tools for understanding programming language(s) or building programs. It does, however, offer features that help track when changes were made and by whom. It also allows you to archive older versions.

When file sharing, subversion can be utilized with either a lock-modify-unlock model (serialized access), or a copy-modify-merge model. While Subversion is primarily a copy-modify-merge system, it still recognizes the need to lock an occasional file, and thus provides mechanisms for this.

Revisions

Revisions: Each time the repository accepts a commit, this creates a new state of the filesystem tree, called a revision. Each revision is assigned a unique natural number, one greater than the number assigned to the previous revision. The initial revision of a freshly created repository is numbered 0 and consists of nothing but an empty root directory.

Updates and commits are separate: One of the fundamental rules of Subversion is that a “push” action does not cause a “pull” nor vice versa.

Files

Subversion can manage any sort of file collection

A version control system (or revision control system) is a system that tracks incremental versions (revisions) of files and, in some cases, directories over time.

A VCS is useful because it allows you to explore the changes which results in each of those versiona dn facilitates the arbitrary recall of the same.

A repository is the central store of a system's data and is at the core of the version control system. Repositories store information in the form of a filesystem tree, a hierarchy of files and directories.

Any number of clients can connect to the repository and read/write to these files.

As the files in the repository are changed, the repository remembers each version of those files.

A version control client has the ability to request previous states of the filesystem from the repository. https://www.coursehero.com/file/17477015/Subversion/

Annotate

Next Chapter
Git
PreviousNext
System & Tools
Powered by Manifold Scholarship. Learn more at
Opens in new tab or windowmanifoldapp.org