This video takes a look at branching in Surround SCM, including the benefits of branching, a review of branch types, and how to create branches. The video also covers promoting and rebasing, which enables code to be sent up or down your branch tree while keeping track of how the code moved between branches.
branching
Perforce introduced the concepts of streams in their upcoming release, and we’ve had a few folks ask us how they compare with Surround SCM‘s implementation of branches.
I gathered some highlights on streams from their blog posts, and I’d like to compare these highlights to existing Surround SCM features. As you’ll see, many of the new features that Perforce streams provide have been part of Surround SCM branches for years.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
The customers and prospects we typically work with are medium-sized and larger businesses that understand the business value of Agile, but are leery of going “all in” right away. What we see in these cases is a slow transition where they evaluate various Agile practices, keeping only the ones that improve team productivity without hampering their ability to meet existing quality, reporting, and compliance requirements.
One area where we can help is with tooling for these companies in transition. Seapine ALM provides an alternative between legacy systems built on Waterfall concepts and pure Agile tools that focus almost exclusively on the project management side of Agile. Surround SCM, an integrated source control and change management tool, is a key component of Seapine ALM for developers.
Fernando Cremer, a product consultant here at Seapine, will be demonstrating how an integrated solution like Seapine ALM can support your adoption of Agile practices. Some of what he’ll cover in Surround SCM includes:
- Flexible branching models that support rapid development and refactoring
- The benefits of linking code changes with stories and issues in TestTrack
- Using continuous integration tools with Surround SCM
If you’re struggling to make a tool like Subversion or Git work in a hybrid development environment, join us for this webinar.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponIf you use a robust software configuration management system like Surround SCM, chances are you are using branches. Changes made in one branch usually need to make it to another branch. Surround SCM offers different ways to merge these changes.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
It’s fall in Ohio, and raking the leaves is a critical task if you want to stay on good terms with your neighbors. It’s easy to let them pile up until getting through your yard becomes an exercise in futility. The same can be true with wading through your Surround SCM branch tree if you have a lot of branches. Surround SCM includes a number of ways to manage the branch tree, which should be performed on a regular basis if you want to keep things running smoothly for your users.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponDuplicating changes across branches is critical to streamlining your development efforts because it eliminates the need to manually make the same change in multiple locations. Surround SCM’s Duplicate Change functionality allows you to take a change associated with a TestTrack defect, changelist, label, or a set of files and copy it to any branch in the tree. This video provides an overview of this feature.
Works with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
SSCMigrate is a sample tool that copies a branch into a new mainline. It can be any branch, however, only that branch is migrated. Any child branch will not be migrated. This is a sample tool and it is not a finished product by any means.
Depending on your needs, this may give you a good starting point.
Continue reading…
Works with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
MergeByDefect is an application that takes advantage of Surround SCM’s plugin architecture and API to give the user a tool to merge changes related to a TestTrack defect with the same file on another branch.
This application was originally posted as SSCM Bug Merge, which required a lot of manual input. MergeByDefect takes advantage of environment variables made available through the plugin architecture and the Surround SCM API to eliminate manual input.
Continue reading…
Recently I posted a Java application called CM Toolbox on our labs site. The application allows you to select a Surround SCM branch and then get a list of TestTrack Pro items that have files attached from the selected branch. There is also the ability to use a TestTrack Pro filter, to limit the defects that are queried. For example, you may not care about items that are closed.
Continue reading…
Works with TestTrack 2009 and Surround SCM 2009
A few days ago I posted an article on how to create a defect list using Java. This builds on top of that, bringing in Surround SCM.
This application will show you only defects that have files attached from the specified branch. Used in conjunction with TestTrack filters, this application can give you the list of files you are looking for.
Continue reading…
