Ctrip Mini Program Collaborative Development: Repository Management, CI/CD, and Continuous Delivery

Background: Ctrip’s mini‑program ecosystem now includes over 30 business lines with hundreds of developers and a bi‑weekly release cadence, creating a need for faster, more reliable delivery mechanisms.

Collaborative Workflow: The team adopts a modular approach, splitting code into independent Git repositories (bundles) per business unit, which are merged in a dedicated release repository to produce a complete mini‑program.

Repository Management: Each bundle follows strict naming (e.g., weixin-pages‑ ), branch (master as release), file, and commit conventions. An app.json in each bundle defines routing, which is merged during packaging using the internal miniTools scaffolding tool (e.g., minitTools —init ).

Continuous Integration: Leveraging the official miniprogram‑ci tool and a GitLab CI pipeline, the process triggers on pushes to the master branch. The .gitlab-ci.yml configuration updates submodules, runs ESLint, compiles the code, checks package size, validates release‑candidate (RC) flags, and uploads the build artifacts. Key pipeline steps are illustrated in the accompanying diagrams.

Continuous Delivery: The final build is handed over to Ctrip’s internal MCD release platform, where a pre‑configured Python script extracts the zip from the release branch, generates a preview QR code, and notifies the PMO. After testing, the PMO manually submits the package to the WeChat backend for review.

Summary: By automating repository management, CI, and CD, developers only need to commit code; packaging, testing, preview generation, and notifications are handled automatically, reducing manual effort, minimizing errors, and enabling agile, coordinated development across dozens of mini‑program business lines.