Artifacts
Keep the files your runs produce, per run, on your computer.
Artifacts are files a run produces that you want to keep — an installer, a zip, a test report. CID stores them per run in its own data folder:
Artifacts folder
%APPDATA%\cid\artifacts\<project>\<workflow>\run-<number>\Two ways to keep files
- List them on the workflow. In the workflow editor's Artifacts section, add one path per line. Relative paths start from the project folder (or the remote deploy path on a server), and
*works in file names, e.g.dist\*.zip. After a successful run, CID copies the matches in. On a server workflow they're downloaded over SFTP. - Write them from a step. Steps that run on this computer get a
CID_ARTIFACTS_DIRenvironment variable pointing at this run's folder — copy files there yourself, e.g.Copy-Item app.zip $env:CID_ARTIFACTS_DIR.
Finding them
- The run panel lists a run's artifacts with their sizes and an Open folder button.
- Settings → Artifacts folder shows where the whole folder is, with an Open folder button.
- Runs that kept nothing don't leave an empty folder behind.
Paths that match nothing are reported in the run's Collecting artifacts log but don't fail the run. Folders on a server can't be downloaded — zip them in a step first.
Something missing or wrong here? Let us know
