Releasing an Environment Through the CloudNativeRelease Extension

Releasing an Environment Through the CloudNativeRelease Extension

1. Configure a pipeline.
2. Add the CloudNativeRelease extension to the pipeline. For details, see Table 1.

   This extension allows you to orchestrate environment release policies in CCE clusters. There are rolling upgrade release and grayscale release.

   Figure 1 Configuring CloudNativeRelease
   

   Table 1 Parameter description

   Parameter	Description
   Name	Extension name Enter only letters, digits, underscores (_), hyphens (-), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses (), and spaces, with a maximum of 128 characters.
   Environment Level	Release environment type. Available environment types: development, test, pre-production, and production.
   Environment	Release 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.

3. Execute the pipeline after the configuration is complete.
4. Click the task card to view the Task Logs and Task Results.
   Figure 2 Checking the execution result
   
   • 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 Environment Release Result.