mirror of https://github.com/containers/podman.git
5fc3d871ad
Using both the 'skip' and 'only_if' features at the same time may be hard for maintainers to decipher. Consolidate them into `only_if` since that bypasses creation of the task all together - meaning there are potentially fewer tasks for a developer to scroll through. Since the `multiarch` Cirrus-Cron build no-longer depends on the direct "build-ability" from the current repo. state, it can be further optimized. When operating in this context, avoid running many/most other tasks, depending instead only on `ext_svc_check`. Finally, add a simple document describing the various runtime contexts along with the list of expected tasks. Reference this prominently right in front of every `only_if` so it's impossible for a maintainer to miss. Signed-off-by: Chris Evich <cevich@redhat.com> |
||
|---|---|---|
| .. | ||
| 99-do-not-use-google-subnets.conflist | ||
| CIModes.md | ||
| cirrus_yaml_test.py | ||
| ext_svc_check.sh | ||
| lib.sh | ||
| logcollector.sh | ||
| logformatter | ||
| logformatter.t | ||
| pr-should-include-tests | ||
| pr-should-include-tests.t | ||
| required_host_ports.txt | ||
| runner.sh | ||
| setup_environment.sh | ||
| shellcheck.sh | ||
| swagger_stack_trace.png | ||
| timestamp.awk | ||
