Skip to content

← All questions

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

Asked 63 views0 answers

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.

asked by Zeynep Arslan64 ·

No answers yet

Know the answer?

Reviewed before it appears. Wrap commands and output in triple backticks and they will render as a code block.

Have a different question? Ask it.

Related