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.
Our wiki has four versions of "the command to run before you merge", the CI file has a fifth, and they disagree about browsers and retries. Every time we change a gate someone has to find all five.
Is there something in SDODS for this, or do I write a Makefile?
Accepted answer
Processes. A process is a named run recipe that lives in the project or workspace YAML:
processes:
- name: pr-check
title: Pull request check
trigger: pr
tags: '@smoke'
browsers: [chromium]
harMode: replay
gates: { minPassRate: 100 }
- name: nightly-regression
trigger: nightly
tags: '@regression'
browsers: [chromium, firefox, webkit]
notify: [github]Then the command everybody types, and the one in CI, is the same short thing:
sdods run -p demo-shop --process pr-checkExplicit flags override the process's fields, so --process nightly-regression -b chromium is a legitimate way to run one browser of a nightly locally.
sdods processes list -p <slug> prints what exists:
Worth knowing where to put them. Processes under defaults.processes in the workspace file apply to every project; a project process with the same name overrides it wholesale.
So the pattern that scales is: the shape of pr-check in the workspace, and only the projects that genuinely differ redefining it. After that a change of gate or browser list is a YAML edit rather than a pull request against your CI file.
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.