Configuration management: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
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 debugging and everything in between, but in the open source world there has been more popular to seperate the "creation time" management tasks into single user [[make]] like utilities and have versioning as a seperate set of multi-user tools and so on so forth. This modular approach has its advantages but | 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 debugging and everything in between, but in the open source world there has been more popular to seperate the "creation time" management tasks into single user [[make]] like utilities and have versioning as a seperate 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. | |||
<!-- | <!-- | ||
In an ideal world a Software Configuration Management '''SCM'' tool would offer: | In an ideal world a Software Configuration Management '''SCM'' tool would offer: | ||
Revision as of 20:45, 6 March 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 debugging and everything in between, but in the open source world there has been more popular to seperate the "creation time" management tasks into single user make like utilities and have versioning as a seperate 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
Links
- The old comp.software.config-mgmt FAQ - Outdated but contains a few interesting pieces of information