Identical Testing Environments from Laptop to CI with tmt and Testing Farm
summary
Describes concrete changes that make CI runs reproducible: tmt now drives Testing Farm scheduler so a local `tmt run` can provision the same Artemis VM, apply Testing Environment Profiles (Ansible playbooks published to Ansible Galaxy), and run the same plan. An Artifact Install plugin downloads exact RPMs, creates a DNF repo, installs only requested subpackages and verifies versions. Multi‑host pipeline and recipes exist and mostly work, with some edge cases (preinstalled RPMs, Fedora buildroot rollout, policy distribution) still being finalized.
AI-written summary · about
chapters (8)
- 0:00Testing pipeline challenges
- 3:09Testing Farm approach
- 5:17TMT policies and profiles
- 8:11Artifact installation
- 10:16Current status and gaps
- 12:26Reproducing tests with recipes
- 13:29Q&A: local vs Testing Farm
- 17:16Live demo: TMT and Testing Farm
related talks
40mEasily enable tests in Fedora, RHEL, GitHub
35mBoost your testing with Testing Farm
35mImage Mode Support in Testing Farm
14mUsing packit and testing farm for CI/CD and automation in an upstream project
27mAdvanced Multipurpose Infrastructure: A Self-Managed Cloud Environment with HashiCorp Terraform
17mTDD for Infrastructure Code
01h 05mFedora CI Meetup
15mTransforming Testing: The Power of TestOps