Updated on 2025-08-21 GMT+08:00

Before You Start

Welcome to CodeArts Build. CodeArts Build provides an easy-to-use, cloud-based build platform that supports multiple programming languages, helping you achieve continuous delivery with higher efficiency. With just a few clicks, you can easily create, configure, and run build tasks to automate code retrieval, build, and packaging. CodeArts Build also monitors build status in real time.

This document describes how to use application programming interfaces (APIs) to perform CodeArts Build operations, such as running and querying tasks. For details about all supported operations, see API Overview.

Before calling CodeArts Build APIs, ensure that you are familiar with CodeArts Build concepts. For details, see Service Overview.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary with services and regions. For the endpoints of all services, see Regions and Endpoints.

Table 1 lists the CodeArts Build endpoints. Select the one that fits your service needs.

Table 1 CodeArts Build endpoints

Region

ID

Endpoint

LA-Mexico City2

la-north-2

devcloud.la-north-2.myhuaweicloud.com

LA-Sao Paulo1

sa-brazil-1

devcloud.sa-brazil-1.myhuaweicloud.com

AP-Singapore

ap-southeast-3

devcloud.ap-southeast-3.myhuaweicloud.com

Concepts

  • Account

    An account is created upon successful registration with Huawei Cloud. The account has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The account is a payment entity and should not be used directly to perform routine management. For security purposes, create IAM users and grant them permissions for routine management.

  • User

    An Identity and Access Management (IAM) user is created using an account to use cloud services. Each IAM user has its own identity credentials (password and access keys).

    An IAM user can view the account ID and user ID on the My Credentials page of the console. The account name, username, and password will be required for API authentication.

    For details, see Region and AZ.

  • Region

    Regions are divided based on geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within the same region. Regions are classified into universal regions and dedicated regions.

    • A universal region provides universal cloud services for common tenants.
    • A dedicated region provides particular services for specific tenants.
  • AZ

    An availability zone (AZ) contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to support cross-AZ high-availability (HA) systems.

  • Project

    Projects group and isolate resources (including computing, storage, and network resources) across physical regions. A default project is provided for each region, and subprojects can be created under each default project. Users can be granted permissions to access all resources in a specific project.

    For more refined access control, create subprojects under a project and purchase resources in the subprojects. Then you can assign required permissions for users to access only resources in specific subprojects.

  • Build task

    A task used for compilation and build.

  • Enterprise project

    An enterprise project groups and manages enterprise resources in a logically isolated manner. It can contain resources in multiple regions, and allow resources to be added or removed.

    For details about how to obtain enterprise project IDs and features, see Enterprise Management User Guide.