Subversion Key Concepts
You'll need the following key concepts to use Subversion for version control in the Flow Service.
Connecting to a Repository
You and your team connect to a repository that stores the version history. You can configure a Flow Service user's version control settings to connect to a repository. See Configuring Flow Service Users for a guide.
Working with a Working Copy
When you configure version control for a Flow Service user, you check out a local, working copy of the repository into your Flow Service user's home folder. After you check out a working copy, you can take a snapshot of your working copy, saving the snapshot in the repository's version history. You can sync your working copy with the latest changes. You can also view and compare versions of files to see what was changed and who changed it.
Saving Work with Commits
A commit operation communicates your changes to the repository -- additions, modifications, and deletions. Commits are atomic transactions: either the repository accepts all of your changes or it accepts none.
Reviewing Changes in Revisions
A revision is a commit that was accepted into the repository. A revision is a snapshot that captures how the repository's filesystem tree looked after a commit. You can sync your working copy with a revision from the history. You can also get the commit author and commits details from a revision.
The revision number applies to the whole filesystem tree under the home folder, not individual files. Revision numbers are continuous; the first revision is revision 1.
Note
When you view the repository history, you may not see continuous revision numbers. This can happen when you specify a subfolder as the repository URL. You'll only see the revision numbers that affect the subfolder you specify.
Locking, Editing, and Unlocking Projects
You follow a lock-edit-unlock workflow while you design projects under version control. Using locks, you can safely modify Flow Service files without the risk of conflicts.
When you place a lock on a file, you're the only user who can make changes to the file in the repository. You need to commit or remove the lock to edit the file.
Resolving Conflicts
Conflicts may occur when you update your working copy. If another user has published changes that conflict with yours, you need to resolve the conflict, committing or discarding your changes.