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.
Someone wrote our pipeline step defensively:
sdods lint -p demo-shop
if [ "$?" = "1" ]; then echo "lint failed"; exit 1; fiA branch went in last week with two scenarios missing their suite tag and the step was green. Running it by hand I can see the findings printed, so lint is definitely finding them. What does it actually exit with?
Accepted answer
3. Lint errors get their own code precisely so a pipeline can tell "your features are wrong" apart from "a test failed" and from "your config is wrong":
0 success1 failure — scenario failures, a gate not met, an unexpected runtime error2 configuration or usage error — unknown project, missing environment file, invalid YAML, bad flag value3 lint errors, including when sdods run lints first130 cancelledSo delete the if entirely and let the non-zero exit fail the step:
sdods lint -p demo-shopIf you want the findings as data rather than as text, --json gives you { ok, errors, warnings, filesChecked } on stdout and you can key off ok.
Full table: Exit codes.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.