From Code to Production: How Alibaba Automates Deployment with Aone

From Source Code to Production

The term "program" can refer to source code, an installation package, or a running service; only when the code is built, packaged, and deployed does it provide value to users.

Challenges of Large‑Scale Deployment

Imagine a CTO receiving five flawless Git repositories that each produce a WAR package and must be deployed to 100 servers each, with continuous feature additions requiring rolling updates without downtime.

Aone – Alibaba’s Integrated Platform

Aone (renamed CloudEffect in 2017) offers a one‑stop solution: register a new application, initialize the runtime environment, build the WAR, and deploy it to target servers with a single click, handling both initial releases and subsequent updates.

Key Terminology

Application : the runtime instance of a built package, typically one‑to‑one with a Git repository.

Second‑party package : internal packages from other Alibaba teams, stored in Nexus/Yum repositories.

Product / Product line / Product tree : a hierarchy where a product consists of one or more applications, forming a tree rooted at Alibaba.

Change : a feature branch or operational modification; multiple changes are aggregated for integration.

Release : deployment of a version to any environment (test, pre‑release, production).

Quality Assurance Quadrant

The four‑quadrant model maps source‑code vs. runtime on the horizontal axis and automation vs. manual on the vertical axis, covering:

Automated static analysis (e.g., Sonar, PMD) for source code.

Manual code review and security review.

Automated testing (unit, integration, UI, performance) for running programs.

Manual testing supported by test‑case management tools.

Aone’s Laboratory (formerly CISE) integrates these tools, providing static analysis, test execution, and test‑case management.

Test Environment Isolation

To simulate real environments without prohibitive cost, Alibaba shares a large test cluster but isolates each developer’s view using middleware, allowing independent deployment of feature versions while preventing interference.

Pipelines

Pipelines chain tasks such as build, test, approval, and deployment across environments (daily, pre‑release, production). They enforce quality gates like code review and security checks, and support different frequencies for various stages, embodying continuous delivery principles.

Conclusion

The article outlines the end‑to‑end workflow from source code to production, presents quality‑assurance methods and their tool support, and demonstrates how Aone’s pipeline and environment‑isolation capabilities enable a complete continuous‑delivery solution for Alibaba engineers.