Download surround scm

Open topic with navigation You can integrate Surround SCM with issue tracking tools to provide a complete change management solution by tracking what changed and why. This allows you to attach source code files from Surround SCM to issues or items managed in an external issue tracking tool. You can also view and fix issues from Surround SCM. When Surround SCM is integrated with an issue tracking tool, you can analyze risk in source files to determine which files may have unresolved problems based on the issue attachment history. See Analyzing issue risk in files. A server plug-in for the issue tracking integration must be installed in the issueplugins folder in the Surround SCM application directory. See Issue Tracking API documentation in the issueplugins folder in the Surround SCM application directory for information about creating plug-ins. Note: Download plug-ins for Bugzilla, JIRA, and Microsoft Team Foundation Server (TFS) from the Integrations page.

You must map a repository to a working directory before you can work with files. When you get or check out files, they are saved in the working directory. Repositories and working directories serve different purposes. A repository is part of the Surround SCM database managed by the Surround SCM Server. A repository often reflects the directory structure of a project. Repositories organize and group files and subrepositories. A working directory is the local folder on your hard drive that a repository is mapped to. The working directory generally mirrors the repository structure. The working directory is generally mapped to a local drive directory, but can be mapped to a different location, such as a network drive. 1. Select the repository to set the working directory for. 2. Choose Repository > Set Working Directory. The Set Working Directory dialog box opens. 3. Enter a Working directory path or click Browse to select a directory. 4. Select Allow child repositories to inherit this working directory if you want child repositories to use the same directory. The working directory is set automatically when subrepositories are added. For example, if the repository structure is MyProject/src/lib/common and you set the working directory for the MyProject repository to C:\MyProject, the resulting working directory is C:\MyProject\src\lib\common. 5. Select Inherit working directory from parent to use the parent repository’s working directory. The working directory is set as \ . 6. Select Get files to working directory to retrieve a copy of the files to the working directory. Files in subrepositories are also copied to local directories if the Allow child repositories to inherit this working directory option is selected. If the local directories do not exist, you are prompted to create them. See Creating local directories. 7. Click OK to set the working directory. You are prompted to resolve conflicts if you reuse a working directory. Click Remove to remove the existing setting and switch the working directory to the new repository. Click Don't Remove to keep the existing setting and then select a directory not used for other repositories. We recommend setting working directories to a hard drive local to the Surround SCM desktop client or CLI to avoid permission issues. On a Windows computer, setting a working directory to a Samba share can result in permission issues depending on the configuration of ACL support on the Samba share. Specifying a network share for a working directory can have similar issues because the share may use a NAS or Samba on the server side. In these situations, the Surround SCM client on Windows may not be able to properly update the .MySCMServerInfo file when the Unix-based network share marks the file as hidden or read-only.A working directory should be specific to an individual Surround SCM user, so using a network location shared by other users is not recommended. To allow other users to view the files, consider using shadow folders in Surround SCM. See Configuring shadow folders.

Depending on your role and security permissions, you can typically perform the following tasks to modify Surround SCM files. 1. Check out files to make changes to them. If you decide not to edit or save changes in a checked out file, undo the check out. 2. Edit files from the working directory or directly in Surround SCM to update the contents. 3. When you finish updating files, check them in to back up your work and share the changes with other users. 4. If you create new files as you work, add them to Surround SCM to make them available to other users. You may also be able to perform the following tasks to modify files. Roll back files to revert to a previous version. Set custom fields to provide additional file information that your organization wants to track. You can also perform bulk custom field changes to set custom fields for multiple files at the same time. Change the state of files to move them through the configured workflow. Move files to other repositories on the same branch. Rename files to update filenames without affecting historical file information. Remove files that are no longer needed. You can also restore files removed by mistake or destroy files to permanently delete them.

HomeDBmaestro Database Source Control vs. Helix Core vs. Surround SCMDBmaestro Database Source Control vs Helix Core vs Surround SCM comparisonDBmaestro and Perforce are both solutions in the Version Control category. DBmaestro is ranked #13, while Perforce is ranked #8 with an average rating of 7.0. DBmaestro holds a 0.8% mindshare in VC, compared to Perforce’s 1.3% mindshare. Additionally, 100% of DBmaestro users are willing to recommend the solution, compared to 100% of Perforce users who would recommend it. Comparison Buyer's GuideWe performed a comparison between DBmaestro Database Source Control, Helix Core, and Surround SCM based on real PeerSpot user reviews.Find out what your peers are saying about Atlassian, GitHub, Git and others in Version Control.To learn more, read our detailed Version Control Report (Updated: February 2025).Review summaries and opinionsMindshare comparisonAs of March 2025, in the Version Control category, the mindshare of DBmaestro Database Source Control is 0.8%, up from 0.4% compared to the previous year. The mindshare of Helix Core is 1.3%, down from 1.8% compared to the previous year. The mindshare of Surround SCM is 1.6%, down from 1.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.Featured ReviewsUse our free recommendation engine to learn which Version Control solutions are best for your needs.842,145 professionals have used our research since 2012.Top IndustriesCompany SizeQuestions from the CommunityComparisonsProduct ReportsAlso Known AsOverviewSample Customers Find out what your peers are saying about Atlassian, GitHub, Git and others in Version Control. Updated: February 2025.842,145 professionals have used our research