Back to changelog

Run attachments

Attach server logs, build output and merged reports to a CI run, and find every file of the run on its new Attachments tab.

Run attachments

Some files you need to debug a CI failure don't belong to any one test: the server log of each CI machine, the Docker logs, the merged HTML report. They used to stay in your CI provider's artifacts, a login and a few clicks away from the test results.

Now you can attach them to the run in Currents, straight from the CI job, with the record key the job already uses:

npx currents run attach --machine-id shard-1 --caption "Web server log" server.log
The Attachments tab of a run: the files attached to the whole run, grouped by CI machine, then the screenshots, videos and traces of each failed and flaky test
The files of the whole run come first, grouped by CI machine, then the files of each test.
  • Attachments tab — every file of the run in one list: the files you attached, and each test's screenshots, videos and traces from the reporter
  • Grouped by machine — files attached with --machine-id are listed under that machine
  • Search and filter — by file name, caption, spec file, test title or machine, by file type, or by who added the file
  • Open in place — screenshots and videos open in a viewer, traces open in the trace viewer, and text files preview in the list
  • Any level — attach to the whole run, a spec file, a test, or one attempt of a test
  • For agents — the Currents MCP server lists the run's files with a link to each, and currents-add-attachments lets an agent attach files itself

Set CURRENTS_CI_BUILD_ID on the CI job, so the step that reports results and the step that attaches files find the same run. currents run attach ships in @currents/cmd 2.0.