Skip to content

ezgh obs sourcemaps upload

Upload a build's source maps and JS files for a release.

Updated View as Markdown
ezgh obs sourcemaps upload <dir> --application a --release r [--parallel 8] [--dry-run] [flags]

Upload the source maps and JS files of a build directory that has debug IDs (from inject or @ezghcloud/rum-build) and register them under an application’s release: the release your SDK sends (init({ release })), and the application of the client token. Errors from that release are then symbolicated as they arrive. JS files without a map are skipped.

Files go up in 8 MiB chunks, --parallel at a time, each tried up to 5 times; then they’re registered in commits of up to 1,000 files. Chunks the project already holds aren’t sent again, so an interrupted upload resumes by running the same command again, with nothing kept locally. Uploading the same files again changes nothing. A project holds up to 10 GiB of source maps.

The table lists what was registered; the summary goes to stderr. -o json prints {application, release, files}. In CI, a bot with the ObsSourceMapUploadAccess policy can upload without a stored secret (see “CI without a stored secret: OIDC” in the README).

Part of ezgh obs sourcemaps.

Examples

ezgh obs sourcemaps upload dist --application storefront --release "$GITHUB_SHA"
ezgh obs sourcemaps upload dist --application storefront --release 2026.10.13-4f2a9c1 --dry-run

Flags

Flag Type Default Description
--application string the application, as your client token has it (required)
--dry-run boolean show what would be uploaded, and send nothing
--parallel int 8 chunks uploaded at a time, 1 to 16
--release string the release your SDK sends: your build’s version or commit (required)

This command also takes the global flags.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close