CI/CD Maturity Levels and DevOps Practices in Chinese Enterprises

According to the Cloud Computing Industry Alliance's "China DevOps Status Survey Report 2023", 41.2% of Chinese enterprises have reached the comprehensive level of DevOps maturity, 17.83% are at the excellent level, and 0.85% have achieved the outstanding level, indicating widespread automation and standardization.

The report highlights a decreasing proportion of companies without pipeline tools (from 26.89% to 19.11%) and an increasing adoption of automated pipelines (from 17.11% to 28.16%), showing that pipeline automation is becoming a key tool for continuous delivery.

CI/CD Capability Levels

Level 1

CI/CD

1.1

1.1.1 Construction Goal

Implement CI/CD activities within DevOps processes.

Build CI/CD environment for automated or semi‑automated practice.

Level 2

CI/CD

2.1

2.1.1 Construction Goal

Establish CI/CD practice standards and keep them updated.

Standard‑first approach helps teams normalize build and integration activities.

2.1.2 Typical Activities

Sort existing CI/CD standards.

Sort existing CI/CD tool platforms.

Confirm CI/CD status and issues.

Define and publish CI/CD engineering standards and grading.

CI/CD

2.2

2.2.1 Construction Goal

Build automated systems to support CI/CD practice.

Continuously build and integrate multiple systems such as configuration management, code review, build, artifact management, automated testing, deployment change, and pipeline systems.

2.2.2 Typical Activities

Build code management and change review system.

Build code quality detection system.

Build compile‑build system.

Build artifact management system.

Build automated testing system.

Build deployment change system.

Build automated pipeline system.

CI/CD 2.3

2.3.1 Construction Goal

Based on standards, achieve CI/CD automation.

Unified standards and platform implementation ensure effective execution and faster promotion.

2.3.2 Typical Activities

Follow CI/CD standards using the platform.

Level 3

CI/CD

3.1

3.1.1 Construction Goal

Integrate CI/CD practice into organizational standards.

Embed CI/CD in development flow so that each stage is continuously tested and validated.

3.1.2 Typical Activities

Local development triggers CI.

Automatic CI before code push to central repo.

Automatic CI before branch merge.

Automatic CI after branch merge.

CI must pass before CD can be triggered.

CI/CD

3.2

3.2.1 Construction Goal

Set CI/CD admission standards.

Continuously enrich CI/CD checks during project progress to improve quality.

3.2.2 Typical Activities

Add unit tests and quality gates.

Add code style checks and quality gates.

Add code security scans and quality gates.

Add code defect scans and quality gates.

Add maintainability checks, cyclomatic complexity, comment rate.

Add code duplication checks and quality gates.

Add P0 automated regression tests and quality gates.

Add test environment deployment for self‑testing.

Add automated regression tests and quality gates.

Add artifact security scanning and quality gates.

Add full‑source security scanning and quality gates.

Add service security scanning and quality gates.

Add various automated test types (performance, stress, stability, etc.) and quality gates.

Add artifact package management standards and quality gates.

CI/CD

3.3

3.3.1 Construction Goal

Periodically review CI/CD processes to improve efficiency.

Address longer execution times, resource consumption, and instability caused by increased CI/CD checks.

3.3.2 Typical Activities

Review current CI/CD processes and practices.

Continuously improve CI/CD automation efficiency.

CI/CD

3.4

3.4.1 Construction Goal

Identify and resolve CI/CD failure issues.

Use various techniques to quickly locate and fix failures.

3.4.2 Typical Activities

Classify CI/CD failure types (program vs platform).

Timely and effective notification of failure to relevant personnel.

Build automated build system to allow continuation after failure.

Level 4

CI/CD

4.1

4.1.1 Construction Goal

Use statistics and quantitative methods to manage CI/CD processes.

Measure CI/CD efficiency, use data‑driven methods to find bottlenecks and solve them.

4.1.2 Typical Activities

Build a R&D data warehouse linked to CI/CD platform.

Define metrics based on CI/CD standards.

Develop and visualize measurement indicators.

Analyze metric data to continuously operate excellent CI/CD practices.

CI/CD Operational Outlook

CI/CD enables faster iteration, higher software quality, and more efficient team collaboration. Future trends include deeper automation across testing, configuration, monitoring, and logging; AI‑driven AIOps for predictive analysis; security integration (DevSecOps); containerization and micro‑services for flexible deployment; observability and monitoring for real‑time performance insights; and cultural shifts toward cross‑functional collaboration and continuous learning.

Observability Engineering

Integrating monitoring tools (e.g., Prometheus, Grafana, ELK) into CI/CD pipelines ensures new services automatically join the monitoring system. Distributed tracing (OpenTracing, OpenTelemetry) captures end‑to‑end call chains. Health and readiness checks validate deployments, while performance and load testing (JMeter, Gatling) verify stability under stress. Defined KPIs and alert thresholds trigger automatic notifications, and a feedback loop continuously refines CI/CD and observability practices.

Reliability Engineering

Reliability engineering embeds comprehensive automated testing, continuous monitoring, and log management into CI/CD. Chaos engineering experiments (Chaos Toolkit, Gremlin) simulate failures to improve resilience. Blue‑green and canary deployments enable safe rollouts with quick rollback. Self‑healing mechanisms (auto‑restart, auto‑scaling, circuit breakers) reduce manual intervention. Security scans, disaster‑recovery drills, and performance testing further ensure stable, secure releases.

Conclusion

CI/CD‑driven operations are moving toward greater automation, intelligence, security, and sustainability, enhancing software delivery speed and quality while expanding the technical horizon of operations. The future will see smarter, more automated, and cost‑effective CI/CD practices that boost innovation, stability, and business competitiveness.

References

[1] GB/T 42560-2023 "System and Software Engineering Development‑Operations Integrated Capability Maturity Model", National Standardization Management Committee

[2] "2023 Enterprise Digital Transformation Technology Development Trend Research Report", China Information Communication Academy

[3] "China DevOps Status Survey Report 2023", Cloud Computing Industry Alliance

[4] "DevOps IT Efficiency New Infrastructure", Gu Huangliang