The flutter/packages repo uses a dynamic recipe, which loads and runs steps from a yaml file in the repo. As soon as the first step fails, the rest of the steps aren't run. That's usually what we want, but flutter/packages#3458 is an example of a case where we want to run regardless. When we migrate Linux tasks from Cirrus to LUCI we'll have more (see use of always: in the repo's current ci.yml).

We should have some way of doing this that's equally dynamic and in-repo. Maybe via an annotation in the yaml file, or maybe a second .ci.yaml property with a second yaml file of "always"-style tasks.

@keyonghan Is this something you could help set up? I don't know enough about recipes to know how to configure this.