SVN (Subversion) logo

SVN (Subversion)

Open Source

Centralised version control system for managing files and directories with linear history.

Visit website

Pricing

Free / Open source

Type

Manual & Automation

// VERDICT

Reach for SVN when a centralised model genuinely fits - large binary assets, strict locking, or an existing SVN estate. Skip it for new projects where Git's distributed model, PR workflows and ecosystem are the norm.

Best for

A centralised version control system (Subversion) - a single source-of-truth server with path-based access control and file locking, suited to large binary assets and centralised workflows.

Avoid when

You want distributed Git workflows (the modern default), PR-based review, or the broadest CI/tooling ecosystem.

CI/CD fit

CI plugins/integrations · centralised checkout · less common in modern pipelines

Team fit

Teams with large binary assets · Centralised-workflow shops · Legacy SVN estates

Setup

Medium

Maintenance

Medium

Learning

Intermediate

Licence

Free / Open source

// BEST FOR

  • A single centralised source of truth
  • Path-based access control
  • File locking for binary assets that can't merge
  • Handling large binaries better than naive Git
  • Maintaining an existing SVN codebase
  • Linear, centralised history

// AVOID WHEN

  • You want distributed Git workflows (modern default)
  • PR-based review and the Git ecosystem matter
  • You need the broadest CI/tooling support
  • Branching/merging flexibility is a priority
  • Offline distributed work is needed
  • You're starting a new project (Git is the norm)

// QUICK START

Set up/access an SVN server -> svn checkout <url> -> edit, svn commit ->
use trunk/branches/tags structure and locking for binaries.

// ALTERNATIVES TO CONSIDER

ToolChoose it when
GitYou want the modern distributed standard with PR workflows.
AWS CodeCommitYou want a managed Git service on AWS.
BitbucketYou want hosted Git with built-in CI/CD.

// FEATURES

  • Centralised repository with monotonic revision numbers
  • Atomic commits and directory versioning
  • Path-based access control
  • Locks for binary files where merging is impractical
  • Tags as cheap copies, not separate constructs

// PROS

  • Simpler mental model than Git for new contributors
  • Strong path-based ACLs suit regulated environments
  • Better than Git for very large binary repositories
  • Maintained as Apache project — long-term stability

// CONS

  • Centralised — needs server connectivity for most operations
  • Branching and merging slower than Git
  • Mindshare has moved decisively to Git

// EXAMPLE QA WORKFLOW

  1. Set up or access an SVN server

  2. Define trunk/branches/tags structure

  3. Check out a working copy

  4. Edit and commit centrally

  5. Use locking for binary assets

  6. Maintain the server, access and backups

// RELATED QA.CODES RESOURCES

Cheat sheets