Sent email to infra explaining the purpose of these jobs and also renamed them.
We can't know the full changes that happen between each run and we don't need to because we already have this info on experimental flow.

The jobs now will be used as extra verification on official / pre releases.

If we want, we might consider implementing some logic to know the diff in terms of RPM versions that changed between each release/build - but that will require a server like Katello or Pulp to manage the repositories

The current system jobs which are not experimental are not functioning anymore as "CI" jobs in a sense that they need to find new regressions.
the reason for that is they are missing the ability to be triggered per change, like the experimental is doing and currently are running on static 'snapshot repo', so in fact they don't provide much value.

However, instead of removing them completely in favor of experimental, we decided to leverage them to run nightly on stable/pre releases and give us indication that official RPMs which usually are built in a different flow than the normal CI also pass OST.

patches are in progress to address this:
https://gerrit.ovirt.org/#/c/70425/ - changing 4.0 to run on stable latest release ( we might want to change it to pre when RC build is in progress )
https://gerrit.ovirt.org/#/c/70424/ - renaming the jobs to reflect the real repos they are using.