CodeArts Pipeline
CodeArts Pipeline
- Service Overview
- Getting Started
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Template management
-
Pipeline Management
- Execute Pipeline
- Obtaining Pipeline Status in Batches
- Obtaining the Pipeline Status/Obtaining Pipeline Execution Details
- Obtaining the Pipeline List/Obtaining the Pipeline Execution Status of a Project
- Deleting a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Execution Records
- Creating a Pipeline Using a Template
- Creates a pipeline.
- Re-trial Run Pipeline
- Pass the manual review.
- Reject to Manual Review
- Querying Pipeline Logs
- Manage by group
- Rule Management
- Tenant-level policy management
- Project-level policy management
-
Tenant-level open source governance policy management
- Creating a Tenant-Level Open Source Governance Policy
- Modifying a Tenant-Level Open Source Governance Policy
- Querying Details About a Tenant-Level Open Source Governance Policy
- Querying the Tenant-Level Open Source Governance Policy List
- Deleting a Tenant-Level Open Source Governance Policy
- Changing the Enabling Status of a Tenant-Level Open Source Governance Policy
- Project-level open source governance policy management
-
Extension Plug-in Management
- Creating a Plug-in Version
- Creating a Plug-in Draft Version
- Creating a publisher
- Update Plug-in Draft
- Releasing a Plug-in Draft
- Updating Basic Plug-in Information
- Releasing a Plug-in
- Binding a Plug-in to a Publisher
- Updating the Plug-in Icon
- Updating the Publisher Icon
- Deleting a Plug-in Draft
- Querying the Publisher List
- Querying Available Publishers
- Querying the List of Optional Plug-ins
- Querying the Basic Plug-in List
- Querying the List of Optional Plug-ins in Pagination Mode
- Listing add-ons
- Query Plug-in Indicator Configuration
- Query Plug-in Input Configuration
- Query Plug-in Output Configuration
- Querying All Plug-in Version Information
- Querying Plug-in Version Details
- Querying the Plug-in Version
- Deleting a publisher
- Querying Publisher Details
- Creating a Basic Plug-in
- Updating Basic Plug-ins
- Deleting a Basic Plug-in
- Uploading Basic Plug-ins
- Querying Basic Plug-in Details
- Appendixes
- Change History
-
FAQs
- Functions
-
Troubleshooting
- The Pipeline Parameter Referenced by the Task Does Not Exist
- Test Suite Was Running
- Failed to Obtain Tenant Information During Code Check Task Execution
- The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
- Scheduled Task of a Pipeline Was Not Triggered
- Run Button Was Unavailable
On this page
Show all
Help Center/
CodeArts Pipeline/
User Guide/
Pipeline Management/
Managing Parameters/
Using Parameters
Using Parameters
Updated on 2023-11-28 GMT+08:00
This section describes how to configure the releaseversion parameter in a pipeline and transfer the parameter to a build task. The operations for other tasks are the same.
Procedure
- Create a build task.
- On the Parameter Configuration tab page, add the releaseversion parameter, set the default value, and enable Runtime Setting.
- On the Build Actions tab page, select Upload to Release Repos and set Release Version as a reference parameter. After you enter $ in the text box, a parameter list is displayed. Select the releaseversion parameter created in the previous step.
- Save the build task.
- Create a blank template pipeline, add the Build extension and select the build task created in previous steps. The new build task parameter releaseversion is displayed.
- Move the cursor to the releaseversion parameter to set it as a pipeline parameter. Alternatively, click OK, switch to the Parameter Configuration tab page, create the pipeline parameter releaseversion, set Type to Auto-increment or String, set a default value, and enable Runtime Setting.
- Switch back to the Task Orchestration tab page, and edit the added build task. Reference the pipeline releaseversion parameter to the build task releaseversion parameter using $.
NOTE:
- Only text parameters for which Runtime Setting is enabled are displayed.
- The parameter reference format is "${ParameterName}". ParameterName specifies the pipeline parameter name. After you enter $ in the parameter text box, the parameter list is automatically displayed.
- You can move the cursor to a parameter name to quickly set the parameter as a pipeline parameter and directly reference the parameter.
- Save the information and click Save and Run. In the displayed dialog box, you can view the running configuration.
For the runtime parameter, the value is the default value specified when you add the parameter. You can change the value as required. When the pipeline is run, the parameter value used in the build task is the value you set here.
- Click Run to execute the pipeline.
Parent topic: Managing Parameters
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.