For information about the flow for the rpm-install-test job:

Below is one of the job variant definition:

- job:
    name: rpm-install-test
    description: "Install the built rpms (f35 variant)"
    run: playbooks/rpm/rpm-install-test.yaml
    branches:
      - f35
    nodeset: fedora-35-vm-medium
    requires:
      - repo
    roles:
      - zuul: zuul-distro-jobs
    vars:
      repos:
        - name: distro-build
          url: https://kojipkgs.fedoraproject.org/repos/f35-build/latest/x86_64/

1/ https://pagure.io/fedora-zuul-jobs/blob/master/f/playbooks/rpm/rpm-install-test.yaml
- Install of zuul-built repo + depends zuul-built repos: https://pagure.io/zuul-distro-jobs/blob/master/f/roles/repo-setup/tasks/main.yaml
- Install of extra repo (used to set the compose repo url) https://pagure.io/zuul-distro-jobs/blob/master/f/roles/extra-repos-setup
- Run the installation of built packages: https://pagure.io/zuul-distro-jobs/blob/master/f/roles/repo-install-rpm/tasks/main.yaml

repo-install-rpm brings some logic that took some time build and perhaps the same should be re-implemented in the TF job.

@msrb can you provide some input? Before jumping into any work, we need to discuss if this is not something in theory mini-tps (aka instalability) could do?

For packages without tests, this is the most useful job. What is it going to be replaced with? Please don't just remove it without replacement.

Nothing is not an option of course.

We should use here OSCI installability test ideally (fine tuned for repositories produced by Zuul):

https://github.com/fedora-ci/installability-pipeline

If not, then something like packit installability test (fine tuned for repositories Zuul):

https://gitlab.com/testing-farm/tests/-/tree/main/packit

The former is anyway needed or already done for CentOS Stream Zuul?

@msrb kind ping

Indeed, installability test is planned for CentOS Stream and it can be then reused in Fedora as well.

Trying to propose removal now

Trying to propose removal now

Without a replacement?

@churchyard artifact installation is happening during functional testing anyway, is that for now not enough?

Insatllability test currently happens also for packages with no tests. I don't have statistics, but I'd say the majority of the packages have no tests (STI or TMT/FMF), hence the installability test was the only "test" beyond the scratch build.

ok, I will talk to @msrb how to contribute to get it running

It turned out that the only missing piece was the trigger:
https://github.com/fedora-ci/dist-git-build-pipeline/pull/37
Tested here:
https://src.fedoraproject.org/rpms/golang-github-task-slim-sprig/pull-request/3