Testing Farm Konflux CI integration
summary
Shows a concrete, working integration that automates functional tests of container images and RPMs by running a shared Tekton pipeline inside Konflux CI and creating a per-merge-request Konflux cluster for each run. The pipeline has four tasks — preprocess (generate pull-secret name), scheduler (build Testing Farm request via the testing-farm CLI), wait-for-results (parse output), and a workaround to fail CI on nonzero test status — end-to-end runs take about 20 minutes.
AI-written summary · about
chapters (12)
- 0:00Testing Farm and Conflux CI
- 1:48How Testing Farm integrates with Conflux CI
- 3:14Integration pipeline tasks
- 6:58Conflux CI setup for containers
- 8:23Integration challenges and fixes
- 9:50Automated testing workflow
- 15:23Q&A: Security & packages
- 18:13Q&A: Generalizing solution
- 19:24Q&A: Conflux CI permissions
- 21:13Q&A: Fedora packaging for Go
- 22:19Q&A: Testing plans UX
- 24:05Closing
related talks
35mYocto Continuous Integration in a Kube
49mServerless CI/CD for Kubernetes with Tekton
39mKubernetes-centric CI/CD
29mCloud Native CD Pipelines with Tekton
40mLet Your Software Supply Chain Ride with Kubernetes CI/CD
36mModern CI/CD with Tekton and Prow Automated via Jenkins X
47mTekton, a new approach to pipelines
39mPower-Up With Clouds And Pipelines