หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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.
Configuring an Environment Variable
You can use ${variable name} to reference an environment variable when creating or editing a release policy, or use {{variable name}} to reference an environment variable in YAML files. Environment variables include:
- Custom variables: can be added as needed. Currently, only variables of the string type are supported.
- Default variables: system parameters, which cannot be deleted or modified.
Table 1 Default variables Variable
Description
ARTIFACT
Artifact path. In the deployment YAML file, use {{ARTIFACT}} to reference the build artifacts.
TIMESTAMP
Timestamp when the extension is executed. For example, 20230401095436.
PROJECT_ID
ID of the project to which the environment belongs.
Configuring an Environment Variable
- Access the release environment list page.
- Click an environment name. The Environment Information page is displayed.
- Click the Environment Variable tab.
- Click Edit Variable to add a variable and set parameters.
Table 2 Parameters for creating a custom variable Parameter
Description
Variable
Variable name. Enter only letters, digits, underscores (_), and hyphens (-) with a maximum of 128 characters.
Type
Only the string type is supported.
Value
The current value of a variable, or empty if you are adding a new variable. The value contains no more than 512 characters.
Change Value
Updated value of the environment variable.
Description
Variable description. It can contain a maximum of 128 characters.
Private Variable
If a parameter is private, the system encrypts the parameter for storage and decrypts the parameter for usage. Private parameters will not be displayed in run logs.
- Click
in the Operation column to delete a variable.
- Click
to add a variable.
- Click
- After setting all parameters, click Save. The Save Changes dialog box is displayed.
- Confirm the variable information, enter the remarks, and click OK.
You can click the Versions tab to check variable versions.
- Click a version name to view the variable details.
- Click
in the Operation column to compare the current version with a specified version.
Using an Environment Variable
You can use environment variables in the following scenarios:
- When configuring a release policy, you can use ${variable name} to reference an environment variable in the YAML path, for example, the workload YAML path in the rolling upgrade task.
Figure 1 Referencing an environment variable
- Use {{variable name}} to reference an environment variable in the YAML configuration file associated with the release policy.
Figure 2 Referencing an environment variable
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