Source Code Control Tools: Difference between revisions
Joerg.hampel (talk | contribs) Moves VCS to separate page, adds stand-alone tools |
Drjdpowell (talk | contribs) No edit summary |
||
| Line 25: | Line 25: | ||
* [https://tortoisesvn.net TortoiseSvn] for use with [[Subversion]] | * [https://tortoisesvn.net TortoiseSvn] for use with [[Subversion]] | ||
* [https://www.sourcetreeapp.com SourceTree] for use with [[Git]] | * [https://www.sourcetreeapp.com SourceTree] for use with [[Git]] and [[HG]] | ||
[[Category:SCC]] | [[Category:SCC]] | ||
Revision as of 18:53, 20 June 2019
Source Code Control Tools are used to interact with Version Control Systems.
Direct LabVIEW interfaces
The LabVIEW 8.6 help includes a list of SCC tools that integrate with LabVIEW's source code control interface: [1]
Agent SVN
Perforce
Microsoft Visual SourceSafe
Microsoft Team System
MKS Source Integrity
IBM Rational ClearCase
Serena Version Manager (PVCS)
Seapine Surrond SCM
Borland StarTeam
Telelogic Synergy
PushOK (CVS and SVN plugins)
ionForge Evolution
This page offers a comparison of different tools:
SCC Tool Comparison
Stand-Alone Tools
Depending on the Version Control System used, there are usually various third-party tools that offer additional features or platform-specific UX. Popular examples are
- TortoiseSvn for use with Subversion
- SourceTree for use with Git and HG