We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 14 since January 2026, each linked to its source.
datadog-ciWhen uploading .NET MAUI Portable PDBs for managed C# exception symbolication, set `DATADOG_API_KEY` in the environment or `apiKey` in `datadog-ci.json`. Run `datadog-ci ppdb-symbols upload <location> --debug-id-manifest <path>` with the build-time manifest from `dd-sdk-maui`.
datadog-ci ppdb-symbols upload <location> --debug-id-manifest <path>When instrumenting a Cloud Run service for automatic APM, run `datadog-ci cloud-run instrument` with `--tracing inject` and the project, region, and service. Add `--language <language>` to select Java, Node.js, .NET, Python, Ruby, or PHP; omit it for language detection.
datadog-ci cloud-run instrument --project <gcp-project> --region <gcp-region> --service <service-name> --tracing injectWhen a sourcemap is missing from the Datadog UI, locate local `*.js.map` files by top-level `debug_id` or find maps without that field. Run `datadog-ci sourcemaps find` with the build directory and the appropriate query flag; it only inspects local files.
datadog-ci sourcemaps find ./build --debug-id 12345678-1234-1234-1234-123456789abcAfter building JavaScript bundles and sourcemaps, run `datadog-ci sourcemaps inject <build-dir>` before deployment, then upload the same injected artifacts with `datadog-ci sourcemaps upload <build-dir> --debug-id`. Rebuild cleanly after source or build-configuration changes, and keep artifacts unchanged between injection, upload, and deployment.
datadog-ci sourcemaps inject <build-dir>When uploading coverage and excluding selected source files, pass their patterns to `--ignored-source-paths`; the list applies to this upload and replaces the YAML `ignore` list for it.
datadog-ci coverage upload --ignored-source-paths "<pattern1>,<pattern2>" <path> [<another_path> ...]When uploading WASM debug information for Browser SDK stack trace symbolication, provide a `.wasm` file or directory and enable the beta command. The command recursively scans directories and skips files without embedded DWARF sections or a `build_id` section.
DD_BETA_COMMANDS_ENABLED=1 datadog-ci wasm-symbols upload <file-or-directory>When tagging pipeline and job spans in a CI Visibility run, invoke `datadog-ci tag` once with `--level pipeline,job` and the desired tags.
DATADOG_SITE=<site> datadog-ci tag --level pipeline,job --tags <tag1> --tags <tag2>When using datadog-ci v5.20.0 and a workflow needs JSON-formatted output, add the global `--log-format json` option to the command. The official v5.20.0 release note confirms the option was added, but the documentation found does not show a runnable command or specify option placement.
When recording measures or tags in a supported CI provider, set `--level stage` for Azure Pipelines, GitLab, or Jenkins, or `--level step` for GitHub. For Jenkins, update the Datadog plugin to the release required for the new environment variable.
datadog-ci measure --level stage --measures <key>:<number>When Git is unavailable, run `datadog-ci sourcemaps upload` with both `--repository-url` and `--commit-sha` (or their documented environment variables) to bypass Git and upload sourcemaps. The command uses sourcemap source paths directly; its repository root is the directory from which it runs.
datadog-ci sourcemaps upload <sourcemap-directory> --service <service> --minified-path-prefix <prefix> --release-version <version> --repository-url <repository-url> --commit-sha <commit-sha>