Software Configuration Management: Difference between revisions
Redirected page to Configuration management |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Software Configuration Management (''SCM'') tools are toolkits that handle all and any aspects of managing source code. In the commercial world there has been a tendency to integrate all functions of source code management into all singing and all dancing multi-user development toolkits that (potentially) handle anything from initial creation to issue tracking and everything in between, but in the open source world there has been more popular to separate the "creation time" management tasks into single user [[make]] like utilities and have versioning as a separate set of multi-user tools and so on so forth. | |||
This sort of modular approach has its advantages, but the downside is that creating automatic features such as generation of documentation, code and system integration and library management become much harder if not nigh impossible. | |||
==Version control== | |||
;Commercial Tools | |||
*Burton Systems Software: [[TLIB]] | |||
*Computer Associates: Change and Configuration Control (CCC/Manager) | |||
*DuraSoft GmbH: Revision Control Engine (RCE) | |||
*IBM: [[Configuration Management Version Control]] (CMVC) | |||
*Intersolv: [[PVCS|Polytron Version Control System]] (PVCS) | |||
*MKS: Source Integrity | |||
*One Tree Software: [[SourceSafe]] | |||
*Perforce Software: [[Perforce]] | |||
*Thompson Automation Software: Corporate RCS | |||
;Free Tools | |||
*[[Concurrent Versions System]] (CVS) | |||
*[[Revision Control System]] (RCS) | |||
*Source Code Control System (SCCS) | |||
*[[Subversion]] (SVN) | |||
==Build control== | |||
*[[CMake]] | |||
*[[GNU Make]] | |||
*[[kBuild]] - Open Source | |||
*[[Make]] | |||
*[[NMake]] | |||
*[[PAMAKE]] | |||
*Opus Make | |||
==OS/2 Tools== | |||
* [[IBM TeamConnection for OS/2]] | |||
* IBM [[VisualAge TeamConnection]] | |||
* [[Versant Argos]] - IDE for [[VisualWorks]] Smalltalk that had a CM system built in | |||
;Bug & issue trackers | |||
*Apache Bloodhound | |||
*[[Mantis Bug Tracker]] | |||
*[[OS/2 Problem Tracker]] | |||
*Trac | |||
;Language or development tool specific CM tools | |||
* [[AM/ST]] - Configuration management system for [[Smalltalk/V]] | |||
* [[ENVY/Developer]] - For [[Smalltalk]] systems only | |||
==Online software configuration management hosts== | |||
Note that most of these offer only source management and versioning | |||
* [[GitHub]] - Source code repository and version control - Free for open source projects | |||
* [[Netlabs]] - A repository for OS/2 open-source projects - Free | |||
* [[SourceForge]] - The oldest and most flexible of the free source/project sites. | |||
==Articles== | |||
* ''Stefan Ruck:'' [[Manage Your Configuration Files and Data]] - Rudimentary file and project management | |||
==Publications== | |||
* Ben-Menachem: ''Software Configuration Management Guidebook'' - McGraw-Hill 1994, ISBN 0-07-709013-6 | |||
* Jessica Keyes: ''Software Configuration Management'' - 2003, ISBN 0-8493-1976-5 | |||
==Links== | |||
* [http://www.daveeaton.com/scm/ The old comp.software.config-mgmt FAQ] - Outdated but contains a few interesting pieces of information | |||
[[Category:Software Configuration Management]] | |||
Latest revision as of 20:15, 7 August 2023
Software Configuration Management (SCM) tools are toolkits that handle all and any aspects of managing source code. In the commercial world there has been a tendency to integrate all functions of source code management into all singing and all dancing multi-user development toolkits that (potentially) handle anything from initial creation to issue tracking and everything in between, but in the open source world there has been more popular to separate the "creation time" management tasks into single user make like utilities and have versioning as a separate set of multi-user tools and so on so forth.
This sort of modular approach has its advantages, but the downside is that creating automatic features such as generation of documentation, code and system integration and library management become much harder if not nigh impossible.
Version control
- Commercial Tools
- Burton Systems Software: TLIB
- Computer Associates: Change and Configuration Control (CCC/Manager)
- DuraSoft GmbH: Revision Control Engine (RCE)
- IBM: Configuration Management Version Control (CMVC)
- Intersolv: Polytron Version Control System (PVCS)
- MKS: Source Integrity
- One Tree Software: SourceSafe
- Perforce Software: Perforce
- Thompson Automation Software: Corporate RCS
- Free Tools
- Concurrent Versions System (CVS)
- Revision Control System (RCS)
- Source Code Control System (SCCS)
- Subversion (SVN)
Build control
OS/2 Tools
- IBM TeamConnection for OS/2
- IBM VisualAge TeamConnection
- Versant Argos - IDE for VisualWorks Smalltalk that had a CM system built in
- Bug & issue trackers
- Apache Bloodhound
- Mantis Bug Tracker
- OS/2 Problem Tracker
- Trac
- Language or development tool specific CM tools
- AM/ST - Configuration management system for Smalltalk/V
- ENVY/Developer - For Smalltalk systems only
Online software configuration management hosts
Note that most of these offer only source management and versioning
- GitHub - Source code repository and version control - Free for open source projects
- Netlabs - A repository for OS/2 open-source projects - Free
- SourceForge - The oldest and most flexible of the free source/project sites.
Articles
- Stefan Ruck: Manage Your Configuration Files and Data - Rudimentary file and project management
Publications
- Ben-Menachem: Software Configuration Management Guidebook - McGraw-Hill 1994, ISBN 0-07-709013-6
- Jessica Keyes: Software Configuration Management - 2003, ISBN 0-8493-1976-5
Links
- The old comp.software.config-mgmt FAQ - Outdated but contains a few interesting pieces of information