Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- CodeArts Pipeline Usage
- Enabling and Authorizing CodeArts Pipeline
- Accessing CodeArts Pipeline
- Creating a Pipeline
- Configuring a Pipeline
- Grouping Pipelines
- Executing a Pipeline
- Checking a Pipeline
- Configuring a Change-triggered Pipeline
- Managing Pipeline Extensions
- Creating Service Endpoints
- Checking Audit Logs
- Reference
- CodeArts Release User Guide
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Template Management
-
Pipeline Management
- Starting a Pipeline
- Obtaining Pipeline Statuses in Batches
- Obtaining Pipeline Status/Obtaining Pipeline Execution Details
- Obtaining Pipeline List/Pipeline Execution Status in a Project
- Deleting a Pipeline
- Querying Pipeline Details
- Editing a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Execution Records
- Creating a Pipeline With a Template
- Creating a Pipeline
- Retrying a Pipeline
- Passing Manual Review
- Rejecting Manual Review
- Querying Pipeline Logs
- Obtaining the Pipeline Step Execution Output
- Querying Build Products on a Pipeline
- Group Management
- Rule Management
- Tenant-level Policy Management
- Project-level Policy Management
-
Extension Management
- Creating an Extension Version
- Creating an Extension Draft Version
- Creating a Publisher
- Updating an Extension Draft
- Publishing an Extension Draft
- Updating Basic Information of an Extension
- Publishing an Extension
- Binding an Extension to a Publisher
- Updating the Extension Icon
- Updating the Publisher Icon
- Deleting an Extension Draft
- Querying the Publisher List
- Querying the Available Publisher
- Querying the Available Extension List
- Querying the Basic Extension List
- Querying the Available Extensions by Page
- Querying the Extension List
- Querying Extension Indicator Configuration
- Query Extension Input Configuration
- Query Extension Output Configuration
- Querying All Versions of an Extension
- Querying Extension Version Details
- Querying the Extension Version
- Deleting a Publisher
- Querying Publisher Details
- Creating a Basic Extension
- Updating a Basic Extension
- Deleting a Basic Extension
- Uploading a Basic Extension
- Querying the Basic Extension Details
- Template Management (Old Version, Unavailable Soon)
-
Pipeline Management (Old Version, Unavailable Soon)
- Quickly Creating a Pipeline and Jobs with a Template
- Checking the Pipeline Creation Status
- Starting a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Statuses in Batches
- Deleting a Pipeline
- Obtaining the Pipeline List
- Obtaining the Pipeline Status
- Obtaining the Pipeline Execution Status in a Project
- Application Examples
- Appendixes
- Change History
-
FAQs
- Functions
-
Troubleshooting
- Pipeline Fails to Run Because Repository Not Found
- Pipeline Fails to Run Because the Test Suite Is Already in Progress
- Pipeline Fails to Run Because Job Not Found
- Pipeline Is Not Triggered at a Specified Time
- Execution Button Is Unavailable
- Inappropriate Reviewer Configured for the Manual Review Job
- Subpipeline Not Found
- Change-triggered Pipeline Fails to Run and an Error Message Is Returned: "authentication required"
- Pipeline Fails to Run Because Deployment Policy Not Found
- Videos
- General Reference
Copied.
Releasing an Environment Through the CloudNativeRelease Extension
You can use the CloudNativeRelease extension in a pipeline to trigger the configured release policy for releasing an environment.
Releasing an Environment Through the CloudNativeRelease Extension
- Configure a pipeline.
- 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 is 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
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}.
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.
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.
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
