Help Center/ CodeArts Pipeline/ User Guide/ Configuring a Pipeline/ Configuring Pipeline Extensions/ CloudNativeRelease
Updated on 2025-08-13 GMT+08:00
View PDF
Share

CloudNativeRelease

Orchestrate release policies for environments, such as rolling release and grayscale release.

Adding the Extension with GUI

Add the CloudNativeRelease extension when you orchestrate a pipeline. Set parameters as shown in Table 1.

Table 1 Parameter description

Parameter

Description

Name

Extension name, which can be customized.

  • Enter only letters, digits, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), parentheses (), and spaces.
  • Enter 1 to 128 characters.

Environment Level

Release environment type. Available environment types: development, test, pre-production, and production.

Environment

Environment to be released. For details, see Creating a Release Environment.

Artifact Path

Image path for deployment and release. Example: swr.example.com/demo/springboot-helloworld:v1.1. You can use ${} to reference pipeline parameters. Example: swr.example.com/demo/springboot-helloworld:${version}.

Adding the Extension with YAML

Add the CloudNativeRelease extension when you orchestrate a pipeline. Configure the YAML syntax as follows:

  • CloudNativeRelease 
    uses: official_microservice_release
with:
  categories: 8dc56cd6c2cf44029181f04025ed173a
  env_id: 39c94e52fb0e4c03af97e3252c68e2a3
  artifact: swr.example.com/demo/springboot-helloworld:v1.1
    • categories: release environment type.
    • env_id: environment to be released.
    • artifact: image path used during deployment.