Configuration Management You Don't Know (1) -- Configuration Management Concept

Configuration Management is a general term for technical and management measures to ensure product consistency, stability, traceability, and rollback during software development.

Configuration management is often ignored because the focus of the software development process is "development.

Many people think that the document andCodeIn version management tools, it is called configuration management.

At most, directory division, permission setting, and check-out rule setting are performed.

To achieve this, only version control is implemented, rather than configuration management.

In addition to the above, configuration management also requires flexibility and timeliness.

In addition, an important role of configuration management is the efficient, fast, and stable release system.

Before starting this chapter, let's take a look at these professional terms.

1. Daily creation (daily build)

2. Continuous Release (continuous integration)

3. Continuous delivery (continuous delivery)

4. Blue green deployment)

5. Canary deployment)

6. Distributed Management (Distributed Control)

7. Trunk, branch, and tags)

Okay, don't worry. We will explain the meanings of these words one by one and their practical applications in the future chapters.

Before reading a detailed chapter, consider whether your organization or team has such roles and practices.

1. Configuration Administrator (Configuration Specialist)

2. Software Configuration Control Board)

3. Pre-release Review (audit before releasing)

4. Final Test (final candidate)

5. Manual of deployment)

If your organization is equipped with the above roles or adopts the above practices, it is necessary to continue reading this series, to find out how these roles and processes reduce organizational efficiency and undermine work outcomes.