Playbooks 07 and 08: after a failed try, a local run of the integration level is a good first step (guideline)

+14 -6

3 Commits

Author	SHA1	Message	Date
jschoubben	8055006ba1	Playbook 07: the two 'never run integration tests on the machine' lines say 'while developing', so the guideline after a failed try no longer contradicts them (review-471) mesh/delivery delivered Details mesh/check pass 8055006ba1f3 on 0e1d0392bc83 \| unit 39 run, 0 kept, 1 skipped \| integration 39 run, 0 kept, 1 skipped \| over bound: unit (slowest unit…	2026-10-23 23:24:15 +02:00
jschoubben	2b53b6a5d2	Playbooks 07 and 08: say the local run after a failed try as a guideline, not a rule (the operator) mesh/delivery superseded: a newer head of the same pull request Details mesh/check pass 2b53b6a5d24a on 656f3af86f37 \| unit 0 run, 39 kept \| integration 0 run, 39 kept \| clone 13s \| composition passed with v0.1.14-0.20	2026-10-23 23:22:21 +02:00
jschoubben	87c338da8e	Playbooks 07 and 08: a failed try or check is run locally at once, so every failure shows in one run, not one per try (the operator, 2026-10-23) mesh/delivery superseded: a newer head of the same pull request Details mesh/check pass 87c338da8eba on 656f3af86f37 \| unit 39 run, 0 kept, 1 skipped \| integration 39 run, 0 kept, 1 skipped \| composition passed	2026-10-23 23:20:27 +02:00

Playbooks 07 and 08: after a failed try, a local run of the integration level is a good first step (guideline) #471