配置管理和版本控制有什么区别？
谁能简单地解释一下配置管理和版本控制之间的区别？从我在各个网站上找到的描述来看，配置管理似乎只是将配置文件放入源代码控制存储库的一个奇特术语。但其他人让我相信还有更复杂的解释。
Can anyone explain in simple terms what the difference is between configuration management and version control? From the descriptions I've been able to find on various websites, it seems like configuration management is just a fancy term for putting your config files in a source control repository. But others lead me to believe there is a more involved explanation.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（9）
版本控制对于配置管理来说是必要的，但还不够。版本控制发生在某些中央或分布式存储库中，但没有说明任何特定版本的部署或使用位置。
配置管理担心如何获取版本控制中的内容并将其一致地部署到适当的位置，主要是 QA 和生产，但也包括足够大的开发操作开发人员。
例如，您可以将所有 SQL 查询保留在版本控制中，包括表修改脚本，但这并不能控制这些脚本何时部署到适当的数据库服务器并与依赖于该脚本的任何其他代码的部署保持同步。在该数据库结构上。
Version control is necessary but not sufficient for configuration management. Version control happens in some central or distributed repository, but says nothing about where any particular version is deployed or used.
Configuration management worries about how to take what is in version control and deploy that consistently to the appropriate places, primarily QA and production, but in a large enough development operation developers as well.
For example, you may keep all of your SQL queries in version control, including your table modification scripts, but that doesn't control when those scripts are deployed to the appropriate database server and kept in sync with the deployment of any other code that relies on that database structure.
配置管理包括但不限于版本控制。
配置管理是您在项目方面需要管理的一切。这包括软件、硬件、测试、文档、发布管理等等。它识别每个最终用户组件，并跟踪从项目第一天到项目结束之日对其提出的和批准的每个更改。
版本控制专门应用于计算机文件。这包括文档、电子表格、电子邮件、源代码等。
Configuration management includes, but is not limited to, version control.
Configuration management is everything that you need to manage in terms of a project. This includes software, hardware, tests, documentation, release management, and more. It identifies every end-user component and tracks every proposed and approved change to it from Day 1 of the project to the day the project ends.
Version control is specifically applied to computer files. This includes documents, spreadsheets, emails, source code, and more.
版本控制是保存文件并保留它们的不同版本，以便您可以看到随时间的变化。
配置管理通常被称为一个整体过程，它跟踪什么服务器上的代码版本、如何设置服务器（以及在许多地方执行此操作的安装脚本）。这是代码进入源代码控制后发生的事情的过程以及如何部署到服务器/桌面等。
Version control is saving files and keeping different versions of them, so you can see the change over time.
Configuration management is generally referred to as an overall process of which keeps track of what version of the code is on what server, how the servers are setup (and the install scripts to do so at many places). It is how process of what happens after the code goes into source control and how gets to deployed to the servers/desktops etc.
配置管理是一个模糊的术语。
在软件中，它往往是版本控制的超集，强调以可重复和可预测的方式产生结果的整个过程。
在计算维护中，它涉及整个网络和一组附加计算机（包括服务器、客户端、路由器...）的配置设置和硬件/固件/软件版本的维护。
在硬件制造中，它甚至代表了上述两者的超集，包括获得产品所需的硬件部件和软件模块，以及制造它们的过程的描述，有时甚至是生产线本身的整个架构和配置。
Configuration management is an ambigute term.
In software, it tends to be a superset of version control with emphasis on the entire process to produce a result in a repeatable and predictible manner.
In computing maintenance, it is related to the maintenance of the configuration settings and hardware/firmware/software versions of entire networks and set of attached computing machines (including servers, clients, routers...).
In hardware manufacturing, it represents even a superset of the two above, including the hardware pieces and software modules needed to obtain a product, with the description of the process to manufacture them, and even sometime the entire schemas and configurations of the production lines themselves.
除了上面所说的之外，我还想推荐 Bob Aiello 的书，名为“配置管理最佳实践” - http://www.amazon.com/dp/0321685865 。
它涵盖了软件配置管理的所有方面，包括版本控制。
In addition to everything said above I'd like to recommend Bob Aiello's book named "Configuration Management Best Practices" - http://www.amazon.com/dp/0321685865 .
It covers all aspects of Software Configuration Management including version control.
版本控制是对可交付成果的控制，而配置管理是管理产生可交付成果的整个过程。配置管理涉及变更管理、项目管理等，一般不是通过简单的版本控制来管理的。
Version control is the control of deliverables whereas configuration management is managing the entire process leading to produce the deliverables. Configuration management involves change management, project management, etc., which generally are not managed by simple version control.
粗略地说，版本控制意味着您可以查看任何特定版本的源代码。配置管理意味着您可以构建和部署并可能测试任何特定版本。
Roughly speaking, version control means you can check out the source for any particular version. Configuration management means you can build and deploy and probably test any particular version.
这可能会有所帮助。
版本和配置
版本：
能够维护对象的多个版本。
常见于许多软件工程和并发工程环境中。
各种版本的合并和协调留给应用程序
有些系统维护版本图
配置：
This can be helpful.
Versions and configurations
Versions:
Ability to maintain several versions of an object.
Commonly found in many software engineering and concurrent engineering environments.
Merging and reconciliation of various versions is left to the application program
Some systems maintain a version graph
Configuration:
版本控制是SCM系统的特征之一。
来自颠覆用户指南：
http://svnbook.red-bean.com/en/1.7/svn -book.html
“某些版本控制系统也是软件配置管理 (SCM) 系统。这些系统专门用于管理源代码树，并具有许多特定于软件开发的功能，例如然而，Subversion 不是这些系统之一，它本身理解编程语言，或者提供构建软件的工具，它是一个可用于管理任何文件集合的通用系统。其他，从杂货购物清单到数字视频混音等等。”
Version control is one of the features of a SCM system.
From the subversion user guide:
http://svnbook.red-bean.com/en/1.7/svn-book.html
"Some version control systems are also software configuration management (SCM) systems. These systems are specifically tailored to manage trees of source code and have many features that are specific to software development—such as natively understanding programming languages, or supplying tools for building software. Subversion, however, is not one of these systems. It is a general system that can be used to manage any collection of files. For you, those files might be source code—for others, anything from grocery shopping lists to digital video mixdowns and beyond."