October 24, 2016

Webinar Recording and Q&A: What’s New in Surround SCM 2016.1

Thanks to everyone who attended What’s New in Surround SCM 2016.1! The webinar recording is now available if you weren’t able to attend or if you would like to watch it again. The edited questions and answers from the webinar follows. https://youtu.be/ZI1iJKakWzQ

Questions & Answers

Q: Do I need a Web server like IIS or Apache to use the Surround SCM Web client?

No, you do not need IIS or Apache, as the Surround SCM architecture is different than the TestTrack Web architecture. The installer includes an SCM Web Server component that runs as a service and listens on a specific port. The URL for end users includes the port number, so the browser points directly to the SCM Web Server component without the need for IIS or Apache.

Q: How does Surround integrate with Jenkins?

Jenkins integrates with Surround SCM through the Surround SCM command line interface. Information about integrating with Jenkins can be found in this knowledgebase article: http://www.seapine.com/knowledgebase/index.php?View=entry&EntryID=761

Q: Are there plans to implement a full Web client with the same functionality as the native client?

The current Web client is not intended for daily usage to change code, but for quick access on other machines. There are no near term plans for a full Web client, but that is still a possibility in the future. If you’re looking for a Web client to allow remote users to connect, remote users can use the Surround SCM native client, which communicates via TCP/IP.

Q: What is the oldest version of Surround we can upgrade to 2016.1?

You can upgrade directly to Surround SCM 2016.1 from Surround SCM 3.0 or later. However, if you are upgrading from version 2008.1 or earlier, it is recommended that you contact Seapine Support for guidance and that you read these two documents before upgrading: http://www.seapine.com/knowledgebase/index.php?View=entry&EntryID=697http://downloads.seapine.com/pub/docs/surroundscmupgradeguide.pdf

Q: Can you associate a file change checked into the Web client against a TestTrack ticket?

That functionality is available in the Surround SCM native client, but is not currently available in Surround SCM Web. The check in functionality via Surround SCM Web is very lightweight and does not currently support integration with TestTrack, changelists, code reviews, or workflow state changes. The Surround SCM Web integration with TestTrack has been captured as a feature request for consideration in a future version.

Q: Can you make the Surround SCM Web client read-only? Or does it match what the users have set as their security group?

The Surround SCM Web client will apply security permissions from the user’s security group, which matches the functionality in the Surround SCM native client. So if a repository/file is read-only based on the security group settings, then it will be read-only in Surround SCM Web.

Q: After committing a changelist, can you set the issue to fixed or closed in Surround?

In the Surround SCM user interface, you can only mark a TestTrack issue as fixed from the TestTrack browser window, which is displayed during an Attach to TestTrack operation. So if you’re attaching the TestTrack item to a committed Surround SCM changelist, then you can mark the issue as fixed at that point. However, after the Attach to TestTrack event is completed, the Surround SCM native client does not have a separate window to allow users to fix TestTrack issues.