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.
NOTE:
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