ac1a919ffd
Rather than manually starting the `ostree-finalize-staged.service` unit, we can leverage systemd's path units for this. It fits quite nicely too, given that we already have a path we drop iif we have a staged deployment. To give some time for the preset to make it to systems, we don't yet drop the explicit call to `systemctl start`. Though we do make it conditional based on a DEBUG env var so that we can actually test it in CI for now. Once we're sure this has propagated, we can drop the `systemctl start` path and the env var together. Closes: #1740 Approved by: cgwalters |
||
|---|---|---|
| .. | ||
| destructive | ||
| nondestructive | ||
| tasks | ||
| README.md | ||
| destructive-ansible.yml | ||
| destructive-unit.yml | ||
| execute_batch.yml | ||
| libinsttest.sh | ||
| libtest-core.sh | ||
| nondestructive.yml | ||
| playbook-run.sh | ||
| provision.sh | ||
| run.sh | ||
README.md
This directory holds tests that use the Fedora Standard Test Interface.
The high level structure is that we take a qcow2 file, inject built RPMs into it, and then use Ansible to run tests.
See .papr.yml for canonical usage.
For local development, you should cache the qcow2 somewhere
stable (outside of this git repo). Also note that ../ci/build-rpms.sh
does not pick up uncommitted changes! Stated more strongly, you
currently need to run build-rpms.sh after every change.
To run just a specific test, use e.g.:
env TEST_SUBJECTS=/path/to/qcow2 ./playbook-run.sh -e tests=.*pull nondestructive.yml