Artifacts and storage
Actions in one run share the execution workspace. Use action outputs to pass exact paths between build, package, archive, and upload steps.
Package build outputs
CPACK_PACKAGE generates DEB, TGZ, TXZ, TZST, ZIP, or STGZ packages from a CPack configuration. It exports the first package path, every generated package path, and the package directory.
For generic files and directories, use:
TARandZIP-
Create archives from workspace-relative paths.
UNTARandUNZIP-
Extract archives into a workspace directory.
Example:
cmake_build -> cmake_test -> package -> upload
The upload action can consume ${package.package_file} without guessing the generated file name.
S3-compatible storage
Use S3_UPLOAD and S3_DOWNLOAD for object storage. Configure the bucket, object key, region, and optional endpoint. Put access keys and session tokens in a secret group instead of ICE.
The actions support custom endpoints, so they can be used with compatible services when their authentication follows the S3 API.
Bunny Storage
BUNNY_STORAGE_UPLOAD-
Upload one workspace file.
BUNNY_STORAGE_DOWNLOAD-
Download one remote file into the workspace.
BUNNY_STORAGE_SYNC-
Recursively upload every file in a directory while preserving relative paths and content types.
BUNNY_PURGE_CACHE-
Invalidate a public Bunny CDN URL after new content is uploaded.
A static-site deployment commonly uses:
build -> storage_sync -> purge_cache
Use the regional Storage API endpoint shown by Bunny when required. The Storage Zone password and Bunny API key are different credentials and should be stored as different secrets.
Paths and diagnostics
Paths are workspace-relative unless an action states otherwise. Prefer outputs such as ${cmake_build.build_directory}, ${package.package_file}, or ${download.local_path} over duplicated path strings.
Every storage action exports status and path metadata. Inspect the first failed action and its outputs when a later action cannot find an artifact.
See Action catalog for the exact parameters and outputs of each action.