Using Cloud Native Release in Pipeline
Cloud native release allows you to orchestrate release policies for environments in CCE clusters (such as rolling upgrade release and grayscale release).
You can use the cloud native release extension in a pipeline to trigger the configured release policy.
Procedure
- When creating or editing a pipeline, add the CloudNativeRelease extension for a job. For details, see Table 1.
Table 1 Parameter description Parameter
Description
Name
Extension name
Environment Level
Release environment type (microservice environment). Available environment types: development, test, pre-production, and production.
Environment
Microservice environment. For details, see Creating a Release Environment.
Artifact Path
Image path for microservice deployment. Example: swr.example.com/demo/springboot-helloworld:v1.1. You can use ${} to reference pipeline parameters. Example: swr.example.com/demo/springboot-helloworld:${version}.
NOTE:SoftWare Repository for Container (SWR) is recommended. You can build an image and push it to SWR through CodeArts Build.
- Execute the pipeline after the configuration is complete.
- Click the task card to view the Task Logs and Task Results.
- Task Logs: displays real-time log information and running status.
- Task Results: displays basic task information, including the service ticket name, ticket ID, and trigger person.
Click the service ticket ID or the View Details button to go to the details page. For details, see Checking the Deployment Result.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot