The Seapine View

A few weeks back I had a conversation with a customer and one of our sales representatives about Surround SCM and file shares.

At the end of the call we reviewed our notes, and the sales rep asked me about shares in Surround SCM, specifically how they work under the hood.

Without hesitation, I found myself creating a drawing on the whiteboard that easily explained how shares work. Honestly, I was amazed that I never thought of this before.  Seemed like an easy way to explain how shares work.
Continue reading…

Applies to Surround SCM 2008 and earlier

Improper understanding of Surround SCM file sharing can lead to undesired situations. This article explains more of what actually occurs in the backend database. It should help you understand how Surround SCM shares files and its benefits.
Continue reading…

It is easy in Surround SCM to share a file from one branch to another, this can be done in one line command inside a trigger. It is much more difficult to create a share from one repository to another repository in the same branch.

The difficulty comes in determining the share to repository location. While the repository paths are identical when sharing between two branches, they are different when sharing between two repositories in the same branch.

This script auto shares files based on input that determines the ShareFrom location and the ShareTo location starting at the repository root (project root) that you want to share.
Continue reading…

File sharing in Surround SCM allows a single copy of a file to exist in multiple repository locations. Since the file is shared, if it is ever updated all locations will reflect those updates simultaneously. There are several best practice suggestions and caveats associated with file sharing. It is important to understand how the Surround SCM architecture facilitates file sharing so that best practice strategies can be devised early on to help you get the most out of file sharing with the least amount of effort.
Continue reading…