Jump to content

Software Configuration Management: Difference between revisions

From EDM2
Ak120 (talk | contribs)
mNo edit summary
Ak120 (talk | contribs)
mNo edit summary
Line 4: Line 4:


==Version control==
==Version control==
;Commercial Tools
*Burton Systems Software: [[TLIB]]
*Burton Systems Software: [[TLIB]]
*Computer Associates: Change and Configuration Control (CCC/Manager)
*Computer Associates: Change and Configuration Control (CCC/Manager)
Line 13: Line 14:
*Thompson Automation Software: Corporate RCS
*Thompson Automation Software: Corporate RCS


==OS/2 Tools==
;Free Tools
* [[IBM TeamConnection for OS/2]]
* IBM [[VisualAge TeamConnection]]
* [[Versant Argos]] - IDE for [[VisualWorks]] Smalltalk that had a CM system built in
 
;Revision control
*[[Concurrent Versions System]] (CVS)
*[[Concurrent Versions System]] (CVS)
*[[Revision Control System]] (RCS)
*[[Revision Control System]] (RCS)
*[[SUBVERSION]]
*[[Subversion]] (SVN)
;Build control
 
==Build control==
*[[CMake]]
*[[CMake]]
*[[GNU Make]]
*[[GNU Make]]
Line 30: Line 27:
*[[PAMAKE]]
*[[PAMAKE]]
*Opus Make
*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
;Bug & issue trackers
*Apache Bloodhound
*Apache Bloodhound

Revision as of 19:57, 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
  • Perforce Software: Perforce
  • Thompson Automation Software: Corporate RCS
Free Tools

Build control

OS/2 Tools

Bug & issue trackers
Language or development tool specific CM tools

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

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