Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ CodeArts Build/ User Guide/ Configuring a Build Task/ Configuring Build Actions/ Uploading a Software Package to Release Repos

Uploading a Software Package to Release Repos

Updated on 2025-01-03 GMT+08:00

For details about the restrictions on uploading software packages, see constraints of CodeArts Artifact.

  • Only files can be uploaded, folders cannot be uploaded, and directories cannot be automatically created.

    For example, the a directory contains the aa file and b directory that contains the bb file, and the build package directory is set to a/**.

    When the a directory is scanned, both aa and bb will be uploaded to the same directory, and the system will not create a b directory in release repos.

  • To upload a folder, package it before adding the Upload to Release Repo action. You can package the folder by running the packaging command or adding the Run Shell Commands action.

Tutorial Video

This video shows how to build with Maven and upload the resulting software package to the release repo using the GUI.

Build on GUI

Add Upload to Release Repo, when configuring build actions. Set the parameters according to Table 1.

NOTE:

When you select Windows executors, add action Upload Software Package to Release Repos (Windows).

Table 1 Parameters for uploading a software package to the release repo

Parameter

Description

Action Name

Assign a custom name to the build action. The name can contain:

  • Letters, digits, hyphens (-), underscores (_), commas (,), semicolons (;), colons (:), periods (.), slashes (/), and parentheses.
  • 1 to 128 characters.

Package Location

Directory for storing the build result.

  • The build package directory supports regular expression matching. ** means that the system recursively traverses the current directory. * indicates zero or multiple characters. ? indicates one character.
  • The system file uses slashes (/) as separators, and the path is not case-sensitive.
Examples:
  • *.class: Matches files whose names end with .class in the current directory.
  • **/*.class: Recursively matches all files whose names end with .class in the current directory.
  • test/a??.java: Matches Java files whose names start with a followed by two characters in the test directory.
  • **/test/**/XYZ*: Recursively matches all files whose parent directory is test and whose names start with XYZ, for example, abc/test/def/ghi/XYZ123.

Version

Optional.

Set the name of the directory where the software package generated by the build task will be uploaded to the release repo.

  • Not specified (recommended): Use the build number to name the directory for storing files uploaded to release repos.
  • Specified: Files in the directory with the same name may be overwritten.

Package Name

Optional.

Set the name for the software package generated by the build task. The name will be used when the package is uploaded to the release repo.

  • Not specified (recommended): Use the original file name to name the file uploaded to release repos. Leave Package Name unspecified so that all files matching the build package directory can be uploaded.
  • Specified: A file may be overwritten when another file with the same name is uploaded. For multiple file uploads with different package names, repeat the upload action for each file.

Custom Directory

Optional.

After you specify the custom upload directory, the uploaded software package is uploaded to the custom upload directory/version number/Software package name directory.

Continue After Failure

Specify whether to proceed after the current action fails by setting the parameter to either Yes or No.

Build with Code

Modify the code in the BUILD block in Creating a YAML File for Your Code-based Build by referring to the following sample code:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
version: 2.0 # The value must be 2.0.
steps:
  BUILD:
    - upload_artifact:
           inputs:
             path: "**/target/*.?ar"
             version: 2.1
             name: packageName
version: 2.0 # The value must be 2.0.
steps:
  BUILD:
    - upload_artifact:
           inputs:
             path: "**/target/*.?ar"
             version: 2.1
             name: packageName
             custom_upload_path: /phoenix-sample-ci/
             ignore_fail: true
Table 2 Parameters in the sample code

Parameter

Type

Description

path

String

Directory for storing the build result.

  • The build package directory supports regular expression matching. ** means that the system recursively traverses the current directory. * indicates zero or multiple characters. ? indicates one character.
  • The system file uses slashes (/) as separators, and the path is not case-sensitive.
Examples:
  • *.class: Matches files whose names end with .class in the current directory.
  • **/*.class: Recursively matches all files whose names end with .class in the current directory.
  • test/a??.java: Matches Java files whose names start with a followed by two characters in the test directory.
  • **/test/**/XYZ*: Recursively matches all files whose parent directory is test and whose names start with XYZ, for example, abc/test/def/ghi/XYZ123.

version

String

Optional.

Enter the release version number.

Not specified (recommended): Use the build number to name the directory for storing files uploaded to release repos.

Specified: Files in the directory with the same name may be overwritten.

name

String

Optional.

Enter the name of the package generated during the build.

Not specified (recommended): Use the original file name to name the file uploaded to release repos.

Specified: A file may be overwritten when another file with the same name is uploaded.

custom_upload_path

String

Optional.

After you specify the custom upload directory, the uploaded software package is uploaded to the custom upload directory/version number/Software package name directory.

ignore_fail

String

Whether to proceed after the current action fails.
  • true: Yes
  • Empty: No

How Release Versions and Package Names Impact Uploads

Figure 1 Impact of an unspecified release version and package name on uploads

Usamos cookies para aprimorar nosso site e sua experiência. Ao continuar a navegar em nosso site, você aceita nossa política de cookies. Saiba mais

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback