Concurrency

Yearly/Monthly

• You can purchase a build concurrency extension in either of the following scenarios:
  • Scenario 1: The number of concurrent tasks exceeds your package limit, and some tasks are queued. In this case, you can purchase a build concurrency extension to improve the capability of handling multiple tasks at the same time and reduce the waiting time.
  • Scenario 2: During builds of a large software project, if the default 2 vCPUs and 8 GB memory configuration does not meet your requirements, you can purchase a large-specification resource package to get stronger computing power and improve build efficiency.
• You can choose custom or built-in executors.
  • Built-in executors: The extension will only increase the number of concurrent builds for built-in executors.

    x86 and Arm executors are supported. Select an executor type that fits your deployment environment. For example, if your software will be deployed to x86 servers, choose x86 executors.

    The two types of executors are available in the following specifications for different scenarios:

    • 2U8G: 2 vCPUs, 8 GB memory, and 60 GB disk space. This specification suits microservice (web/app) builds with no more than 100,000 lines of code (LOC).
    • 4U8G: 4 vCPUs, 8 GB memory, and 100 GB disk space. This specification is ideal for general embedded builds with 100,000–1,000,000 LOC.
    • 8U16G: 8 vCPUs, 16 GB memory, and 100 GB disk space. This specification is designed for embedded builds with 1,000,000–10,000,000 LOC.
    • 16U32G: 16 vCPUs, 32 GB memory, and 500 GB disk space. This specification is optimized for large-scale embedded builds (such as HarmonyOS build) with more than 10 million LOC.
    • 16U64G: 16 vCPUs, 64 GB memory, and 1,000 GB disk space. This specification is suitable for large-scale embedded builds (such as AOSP) with more than 10 million LOC.
  • Custom executors: You provide your own build executors, which are hosted and scheduled by CodeArts Build.

  For details about how to configure hosts in a build task, see Configuring the Build Environment.

• Purchase suggestions:
  • Purchase 1 concurrent build for every 5 developers.
  • If your project uses microservice architecture, purchase 1 concurrent build for every 2 microservices.

1 concurrent execution

• Before purchasing a build concurrency extension, purchase the CodeArts Basic or higher edition package.
• Max. 50 extensions per purchase.

Unit price × Quantity × Purchased duration

Determined by the purchased duration (GMT+08:00). The billing cycle starts from the time you activate or renew your build concurrency extension (accurate to seconds), and ends at 23:59:59 on the expiration day.

For example, if you purchased a build concurrency extension for one month on Mar 08, 2023, 15:50:04, the billing cycle is from Mar 08, 2023, 15:50:04 to Apr 08, 2023, 23:59:59.

Not supported. If your configuration is incorrect, unsubscribe from the feature and purchase it again.

The build concurrency extension will become invalid if not renewed before expiration.

Yearly/Monthly

• If the number of concurrent checks in your CodeArts package does not meet your requirements, purchase a check concurrency extension.
• Purchase suggestions: Purchase 1 concurrent check for every 5 developers.

Number of concurrent executions

• Before purchasing a check concurrency extension, purchase the CodeArts Basic or higher edition package.
• Max. 100 concurrent executions per purchase.

Unit price × Concurrency × Purchased duration

Determined by the purchased duration (GMT+08:00). The billing cycle starts from the time you activate or renew your check concurrency extension (accurate to seconds), and ends at 23:59:59 on the expiration day.

For example, if you purchased a check concurrency extension for one month on Mar 08, 2023, 15:50:04, the billing cycle is from Mar 08, 2023, 15:50:04 to Apr 08, 2023, 23:59:59.

For more information, see Pricing of a Changed Specification.

The check concurrency extension will become invalid if not renewed before expiration.

Yearly/Monthly

• If the number of concurrent pipeline executions in your CodeArts package does not meet your requirements, purchase a pipeline concurrency extension.
• Purchase suggestions:
  • Purchase 1 concurrent pipeline execution for every 5 developers.
  • If your project uses microservice architecture, purchase 1 concurrent pipeline execution for every 2 microservices.

Number of concurrent executions

• Before purchasing a pipeline concurrency extension, purchase the CodeArts Basic or higher edition package.
• Max. 100 concurrent executions per account.

Unit price × Concurrency × Purchased duration

Determined by the purchased duration (GMT+08:00). The billing cycle starts from the time you activate or renew your pipeline concurrency extension (accurate to seconds), and ends at 23:59:59 on the expiration day.

For example, if you purchased a pipeline concurrency extension for one month on Mar 08, 2023, 15:50:04, the billing cycle is from Mar 08, 2023, 15:50:04 to Apr 08, 2023, 23:59:59.

For more information, see Pricing of a Changed Specification.

The pipeline concurrency extension will become invalid if not renewed before expiration.

Yearly/Monthly

• If the number of concurrent deployments in your CodeArts package does not meet your requirements, purchase a deployment concurrency extension.
• Purchase suggestions: Purchase 1 concurrent deployment for every 2 applications.

Number of concurrent executions

• Before purchasing a deployment concurrency extension, purchase the CodeArts Basic or higher edition package.
• Max. 100 concurrent executions per purchase.

Unit price × Concurrency × Purchased duration

Determined by the purchased duration (GMT+08:00). The billing cycle starts from the time you activate or renew your deployment concurrency extension (accurate to seconds), and ends at 23:59:59 on the expiration day.

For example, if you purchased a deployment concurrency extension for one month on Mar 08, 2023, 15:50:04, the billing cycle is from Mar 08, 2023, 15:50:04 to Apr 08, 2023, 23:59:59.

For more information, see Pricing of a Changed Specification.

The deployment concurrency extension will become invalid if not renewed before expiration.