-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
None
When we sync the projects we shipped in Fedora (e.g clients and deps) every release, we tend to hit issues because of :
1. we don't/forgot to backport commit from Fedora distgit (mostly from PR) to RDO one
2. when fixing new issue while building on Rawhide, we don't backport the fixes to RDO distgit
In both case, this lack of reconciliation might lead to regression (e.g [1])
I'd like to add a "DLRN-rpmbuild-fedora-rawhide" in experimental pipeline, that we'd triggered before building the clients in release preparation or at each client u-c bump. That way we'd ensure that everything is running fine before building and syncing.
This would fix the point 2.
To mitigate 1. we'll have to check the new commits on Fedora distgit manually. Other option is to check in the job "DLRN-rpmbuild-fedora-rawhide" the diff between Fedora distgit and RDO distgit, and raise an error if there is an unexpected diff (the hard part is to evaluate correctly this diff).
[1] https://src.fedoraproject.org/rpms/python-oslo-context/pull-request/3
1.
|
Create Zuul job to rebuild on Fedora Rawhide | Closed | Joel Capitao | ||
2.
|
Create Zuul job to rebuild on EPEL9 | Closed | Joel Capitao | ||
3.
|
Add the new jobs to the required project | New | Unassigned | ||
4.
|
Recheck all projects we ship on Fedora to test with new job | New | Unassigned |