mirror of https://github.com/containers/podman.git
8cff1c2bf8
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> |
||
|---|---|---|
| .. | ||
| 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 | ||
