diff options
author | Chris Evich <cevich@redhat.com> | 2022-06-30 12:13:45 -0400 |
---|---|---|
committer | Chris Evich <cevich@redhat.com> | 2022-07-01 11:25:47 -0400 |
commit | 8cff1c2bf834c6a5ef41b4b96c243d0a02c704c8 (patch) | |
tree | af792cfe5def0e8713cab512aea4103beff4bbd8 /cmd/podman/shell_completion_test.go | |
parent | f58d7dbdab7076d1ff83375fdbc010445261c0cd (diff) | |
download | podman-8cff1c2bf834c6a5ef41b4b96c243d0a02c704c8.tar.gz podman-8cff1c2bf834c6a5ef41b4b96c243d0a02c704c8.tar.bz2 podman-8cff1c2bf834c6a5ef41b4b96c243d0a02c704c8.zip |
Cirrus: Add podman-machine integration test
The podman-machine integration tests are designed to execute on
bare-metal, since they perform significant work with virtual-machines.
This test is costly to run at scale, so it is limited to being manually
triggered by developers (for now). A 'trigger' button will appear in the
task status page of the Github WebUI once all test dependencies are met.
In the Cirrus-CI WebUI, there is also a 'pre-trigger' button that may be
pressed if a developer doesn't wish to wait. Also:
* Add a `localmachine` target in the `Makefile` on the off-chance
developers wish to execute locally. Update the `ginkgo-run` target
to accommodate re-use by the new `localmachine` target.
* Exclude `podman_machine` task from `success` dependency verification.
This also involves adding an exception to `cirrus_yaml_test.py`
otherwise it will complain loudly.
* ***NOTE*** Inclusion of `ec2_instance` in *any* task will cause
`hack/get_ci_vm.sh` to barf and be non-functional. Future updates will
be made to restore functionality. Before then, simply comment out
the `ec2_instance` section as a temporarily workaround.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'cmd/podman/shell_completion_test.go')
0 files changed, 0 insertions, 0 deletions