Build a frontend CI/CD system using Function Compute
This topic describes how to use Function Compute to deploy frontend static resources in a decoupled frontend and backend architecture.
Background information
Companies typically use GitLab to host frontend code, configure Jenkins to listen for webhook messages, and then publish to OSS. This solution is flexible, but it has the following disadvantages:
You must purchase servers to build your own Jenkins, which incurs compute and storage fees.
You need professional operations and maintenance (O&M) engineers to ensure stable server operation.
Integrating the OSS SDK is complex.
Solution overview
The solution architecture is as follows:
The solution flow is as follows:
When you commit code to the frontend code repository, Function Compute detects the changes.
Function Compute downloads the committed branch and uploads the files to OSS.
CDN accelerates the delivery of the frontend resources.
Benefits
Serverless: You do not need to purchase or manage servers.
Fully managed: You do not need to deploy or configure Jenkins.
Comprehensive: Includes features such as log query, performance monitoring, and alerts.
Event-driven: Uses triggers to automatically respond to events.
Low cost: Pay as you go. For more information, see Billing overview.
Details
For more information, see Build a frontend CI/CD system using Function Compute.