Help Center/ CodeArts Build/ User Guide (Ally Region)/ User Guide/ Configuring Build Actions/ Uploading a Software Package to Release Repos
Updated on 2026-01-08 GMT+08:00
View PDF
Share

Uploading a Software Package to Release Repos

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

Graphical Build

To upload generated software packages to release repos, add Upload to Release Repo when configuring build actions.

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

  • Only one or more 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.

The parameters are described in the following table.

Parameter

Description

Action Name

Assign a custom name to the build action.

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 separator is a slash /, and the path is case-insensitive.

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

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

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. If the package name needs to be set and multiple files need to be uploaded, add the uploading action for multiple times.

The figure below illustrates the impact of an unspecified release version and package name on uploads.

Code-based Build

1
2
3
4
5
6
7
8
 
version: 2.0 # The value must be 2.0.
steps:
  BUILD:
    - upload_artifact:
           inputs:
             path: "**/target/*.?ar"
             version: 2.1
             name: packageName

Parameter

Type

Description

Mandatory

Default Value

path

String

Directory for storing the build result. A regular expression is supported. Example: **/target/*.?ar uploads all JAR and WAR packages built with Maven.

Yes

None

version

String

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.

No

None

name

String

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.

No

None