Run directory not found after moving the artifacts root, exit 2

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

We moved the artifacts root off the workspace disk on our agents:

bash

sdods run -p rwa-bank -e staging -l hybrid --artifacts-dir /mnt/scratch/sdods-runs

The run is fine and the directory is there with everything in it. The step afterwards that publishes the run to the tracker is not:

bash

sdods integrations notify --run-id 019f3ac0-2b71-7e93-8f04-6ca5d1b2e770

text

Run directory not found: /home/build/work/.sdods/runs/019f3ac0-2b71-7e93-8f04-6ca5d1b2e770
  hint: Pass --artifacts-dir or check the run id (sdods report --last).

Fair enough that --artifacts-dir on run does not carry to the next command. But SDODS_ARTIFACTS_DIR=/mnt/scratch/sdods-runs is exported for the whole job and it does not help either: sdods report --last finds the run under the scratch path, integrations notify still looks under the workspace.

Is the environment variable only honoured by some commands, or am I setting it in the wrong place? Passing --artifacts-dir twice works, I would just like to know which of the two I should stop trusting.

reporting cli

asked by Zeynep Arslan

Run directory not found after moving the artifacts root, exit 2

No answers yet

Know the answer?

Related