Cirrus: Skip deep testing on branches

Previous to this commit, the entire suite of CI tasks run in a PR, run
again for every merge (a.k.a. branch push).  This wastes time and
resources with substantively overlapping testing.  The primary reason
to test on branch-push, is providing coverage for merge-semantics.
In other words, problems introduced due to the sequence of PR merging.
For this purpose, the vast majority of problems can be caught quickly by
a small subset of automated tests.  If deeper debugging is necessary,
then opening a test-PR is a small price to ask for the enormous amount
of time/resource savings with more limited branch-push testing.

Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Chris Evich
2020-10-05 13:22:34 -04:00
parent 1b16fcfd14
commit 81c0bb4b6b

View File

@ -87,6 +87,7 @@ ext_svc_check_task:
automation_task:
alias: 'automation'
name: "Check Automation"
skip: &branch "$CIRRUS_PR == '' || $CIRRUS_TAG != ''" # Don't run for branches
container: *smallcontainer
env:
TEST_FLAVOR: automation
@ -231,6 +232,7 @@ validate_task:
bindings_task:
name: "Test Bindings"
alias: bindings
skip: *branch
depends_on:
- build
gce_instance: *standardvm
@ -419,6 +421,7 @@ local_integration_test_task: &local_integration_test_task
# Integration-test task name convention:
# <int.|sys.> <podman|remote> <Distro NV> <root|rootless>
name: &std_name_fmt "$TEST_FLAVOR $PODBIN_NAME $DISTRO_NV $PRIV_NAME $TEST_ENVIRON"
skip: *branch
alias: local_integration_test
depends_on:
- unit_test
@ -456,6 +459,7 @@ remote_integration_test_task:
container_integration_test_task:
name: *std_name_fmt
alias: container_integration_test
skip: *branch
depends_on:
- unit_test
matrix: &fedora_vm_axis
@ -484,6 +488,7 @@ container_integration_test_task:
rootless_integration_test_task:
name: *std_name_fmt
alias: rootless_integration_test
skip: *branch
depends_on:
- unit_test
matrix: *fedora_vm_axis