diff options
| author | Frantisek Sumsal <frantisek@sumsal.cz> | 2023-07-12 10:59:30 +0200 |
|---|---|---|
| committer | Frantisek Sumsal <frantisek@sumsal.cz> | 2023-11-20 21:45:59 +0100 |
| commit | 04dc383b40669ba380846f387788cede41af30ed (patch) | |
| tree | 91a4b1b47bf287dfb9f1645ad391ab9e73036984 /.packit.yml | |
| parent | test: don't use ddebug() before it's defined (diff) | |
| download | systemd-04dc383b40669ba380846f387788cede41af30ed.tar.xz systemd-04dc383b40669ba380846f387788cede41af30ed.zip | |
packit: run tests on Fedora Rawhide via Testing Farm
Let's utilize the full power of Packit and run some tests with the just
built RPMs. This makes use of the Fedora infrastructure provided by
the Testing Farm project [0][1].
With the current configuration, the `tests` job runs tests from the
Fedora tests repository [2] in a very similar fashion like Ubuntu CI
does, just with different metadata all around it. ATTOW there are only
two tests, which are wrappers around unit tests and integration tests;
the latter one currently runs only nspawn-based tests, since there's no
KVM on the test VMs, and, for now, I'd like to see how well the infra is
going to manage our upstream traffic and how stable the whole thing is
end up being before increasing the work load.
[0] https://docs.testing-farm.io/Testing%20Farm/0.1/index.html
[1] https://packit.dev/docs/configuration/upstream/tests
[2] https://src.fedoraproject.org/tests/systemd
Diffstat (limited to '.packit.yml')
| -rw-r--r-- | .packit.yml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/.packit.yml b/.packit.yml index 1b49ddf284..b886632a95 100644 --- a/.packit.yml +++ b/.packit.yml @@ -44,3 +44,11 @@ jobs: - fedora-rawhide-ppc64le - fedora-rawhide-s390x - fedora-rawhide-x86_64 + +- job: tests + trigger: pull_request + fmf_url: https://src.fedoraproject.org/tests/systemd + fmf_ref: main + tmt_plan: ci + targets: + - fedora-rawhide-x86_64 |