- 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.
Number of Parallel Jobs
Billing Description
CodeArts parallel job extension is billed by the number of parallel jobs.
To learn about the price of CodeArts, visit CodeArts Pricing Details.
|
Billing Item |
Description |
Resource Extension Type |
Billing Formula |
|---|---|---|---|
|
Parallel check jobs |
Total number of parallel executions for all your code check tasks in a region. |
Parallel check extension |
Unit price × Number of parallel jobs × Purchased duration |
|
Parallel pipeline jobs |
Total number of parallel executions for all your pipeline tasks in a region.  NOTE:
This takes effect only for pipeline tasks. Code check and deployment in these tasks consume the parallel job quota of the corresponding service. |
Parallel pipeline extension |
|
|
Parallel deployment jobs |
Total number of parallel executions for all your deployment tasks in a region. |
Parallel deployment extension |
Calculation Example
- Scenario Description
Pipelines X and Y are both started for a tenant.
- Pipeline X: consists of check task a and deployment task c.
- Pipeline Y: consists of check tasks a and b, which are executed in parallel.
- Calculation Method Analysis
- Code check: Task a is executed in both pipelines, consuming 2 parallel check jobs. Task b is also executed, consuming 1 parallel check job. So 3 parallel check jobs are used in total.
- Deployment: Deployment task c consumes 1 parallel deployment job.
- Pipeline: Both pipelines are executed, consuming 2 parallel pipeline jobs.
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
