Concepts
| Glossary | Definition |
|---|---|
| Parameter | Runtime parameter values are specified only when a build task is executed. These parameters are categorized as either custom or system-predefined. For details, see Using Parameters. |
| Service endpoint | A service endpoint extends the platform by enabling connections to third-party services. For example, CodeArts Build uses service endpoints to access Git repositories and obtain project code. You can create, edit, or delete these connections as needed. For details, see Defining a Build Task on GUI. |
| Execution plan | You can define rules to trigger builds automatically. These triggers simplify automatic compilation and build for greater flexibility. For details, see Configuring Schedules. |
| Build template | A template contains the build environment, sample build commands, and parameters for a specific programming language or compilation framework. You can quickly start a build by customizing an existing template, accelerating task setup. For details, see Defining a Build Task on GUI. |
| Action | An action, also referred to as a step, represents an automated stage in a build process. For example, it can take two steps, Build with Maven and Upload to Release Repo, to produce a JAR package automatically in software development. For details, see Defining a Build Task on GUI. |
| Domain ID | This unique identifier is generated when a tenant is created. |
| Region | Regions are divided based on geographical location and network latency. Within the same region, shared public services include Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS). Regions are classified into universal regions and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides services of the same type or only provides services for specific tenants. |
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