Configuration management: Difference between revisions

Revision as of 21:33, 27 June 2016

Configuration management tools or CM's, 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 a 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.

Our links section contains a collection of links to online source management and hosting platforms.

OS/2 Configuration management tools

VisualAge TeamConnection

Revision control

Build control

CMake
GNU Make
kBuild - Open Source - Current
Make
NMake
PAMAKE
Opus Make

Bug & issue trackers

Project management

Trac

Language or development tool specific CM tools

ENVY/Developer - For Smalltalk systems only - Commercial - Discontinued

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.

Local and external articles

Stefan Ruck: Manage Your Configuration Files and Data - Rudimentary file and project managment
The old comp.software.config-mgmt FAQ - Outdated but contains a few interesting pieces of information

@@ Line 20: / Line 20: @@
 * [[Make]]
 * [[NMake]]
+* [[PAMAKE]]
 * [[Opus Make]]
 ;Bug & issue trackers