- Service Overview
- Billing
- Getting Started
-
User Guide
- Preparations
- CodeArts Req
- CodeArts Repo
- CodeArts Pipeline
- CodeArts Check
- CodeArts Build
- CodeArts Artifact
- CodeArts Deploy
- CodeArts TestPlan
- CodeArts PerfTest
-
Best Practices
- Best Practices Summary
-
Using CodeArts to Manage an e-Mall Development Project
- Overview
- Resource Planning
- Process
-
Implementation Procedure
- Preparation
- Step 1: Managing Project Plans
- Step 2: Managing Project Configurations
- Step 3: Writing Code
- Step 4: Checking Code
- Step 5: Building an Application
- Step 6: Deploying an Application (CCE)
- Step 6: Deploying an Application (ECS)
- Step 7: Managing Project Tests
- Step 8: Configuring a Pipeline for Continuous Delivery
- Releasing Resources
-
FAQs
-
General
- How Do I Collect or Archive Project Information Locally After a CodeArts Project Is Complete?
- Why Can't an IAM User View Any CodeArts Projects After Login?
- How Do I View All CodeArts Projects and Members Under My Account as Administrator?
- Will the Tasks Created by a Project Member Be Deleted After the Member Leaves the Project?
- Will a New User with the Same Name as a Deleted User Inherit Their Permissions and Tasks?
- CodeArts Req
- CodeArts Repo
- CodeArts Pipeline
- CodeArts Check
- CodeArts Build
- CodeArts Artifact
- CodeArts Deploy
- CodeArts TestPlan
- CodeArts PerfTest
-
General
- Videos
- General Reference
Copied.
Execution Duration
Billing Description
CodeArts execution duration extension is billed by duration.
To learn about the price of CodeArts, visit CodeArts Pricing Details.
Billing Item |
Description |
Resource Extension Type |
Billing Formula |
---|---|---|---|
Duration |
Total time for which resource-consuming tasks are executed in your account per month. Resource-consuming tasks, such as running Shell commands and uploading reports, require built-in resources of the Pipeline service. Build and check tasks use quotas of the relevant services, so they are not resource-consuming tasks. |
Execution duration extension for resource-consuming pipeline tasks |
Unit price × Duration × Purchased duration |
Calculation Example
- Scenario Description
Pipelines X and Y are both started for a tenant.
- Pipeline X: consists of check task a and Shell command task b. The two tasks take 45s and 12s to complete, respectively.
- Pipeline Y: consists of Shell command task c and build task d. The two tasks take 30s and 86s to complete, respectively.
- Calculation Method Analysis
- Code check task a and build task d do not consume pipeline execution resources, so the two tasks are not counted.
- Shell command tasks b and c consume pipeline execution resources, so the two tasks are counted.
Therefore, after the two pipelines are executed, the execution duration of resource tasks is the sum of the time spent in Shell command tasks b and c, that is, 12s + 30s = 42s.
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