Skip to main content

Artifacts

Artifacts are the files a commit needs to run again: its build, wrapper scripts, trained models or calibration data. Your CI saves them with qa save-artifacts, in the results storage. QA-Board then uses them to redo runs and to tune from the web app, without a checkout or a build.

Save them in CI​

  1. List the files in qaboard.yaml, in named groups of glob patterns:

    qaboard.yaml
    artifacts:
    binary:
    glob: build/my-tool
    configurations:
    globs:
    - configurations/*.json
    - "*.yaml"
  2. In your CI job, save them after the build, before the runs:

    make
    qa save-artifacts
    qa batch ci

qa save-artifacts always saves qaboard.yaml, qa/, the metrics and batches files, and the .envrc files, even without artifacts in qaboard.yaml. Patterns are relative to the project's root.

  • To save only some groups: qa save-artifacts binary. The files qa always saves are then left out.
  • To save other files: qa save-artifacts --file 'build/*'.

Compare them with the reference's​

The commit page's Artifacts & Configs view compares each commit's artifacts with the reference's.

Artifacts & Configurations of the per-channel commit against the first int8 commit: build/flags.json differs, and its diff shows quant_per_channel going from false to true.Artifacts & Configurations of the per-channel commit against the first int8 commit: build/flags.json differs, and its diff shows quant_per_channel going from false to true.
Between two quantization commits, only build/flags.json changed: its diff shows which flags.

Where artifacts are saved: Where is the data saved?. When they are deleted, and how QA-Board recreates them: Deleting old data.