The OSCI team cannot maintain its Fedora CI tests anymore
by Jan Kaluža
Hi everyone,
I'm the Product Owner of the OSCI team. A few years ago, the team set up the Fedora CI tests executed for Pagure PRs and Bodhi updates. Specifically the:
- Fedora CI - scratch build
- Fedora CI - installability
- Fedora CI - dist-git test
- Fedora-ci.koji-build.rpminspect.static-analysis
- Fedora-ci.koji-build.rpmdeplint.static-analysis
These tests run on https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/.
Our intent was to run the same tests as we run in RHEL gating also in Fedora gating. That was the main motivation to introduce these tests a few years ago in Fedora.
The OSCI team’s focus however changed to CentOS Stream after it was introduced and we never had enough capacity to refocus back to Fedora. I do not see any option currently on how the team could keep maintaining our current Fedora infrastructure and tests.
The main reasons for this are simply the amount of work the team can handle in its current head-count and also the differences between the CentOS Stream infrastructure and Fedora infrastructure. We are moving to Gitlab.com CI for CentOS Stream and we cannot do the same move in Fedora. We also cannot maintain both infrastructures at the same time for the reasons mentioned above.
I’m therefore asking anyone who wants to keep these tests running to step in and tell us. We are ready to provide a knowledge transfer if it’s needed, but otherwise, we plan to decommission this Jenkins instance and the tests completely by March 2024.
Thank you for understanding,
Jan Kaluza
5 months
Automatic check for bodhi updates not to break RPM dependencies
by Miro Hrončok
On 07. 11. 23 12:17, Sandro Mani wrote:
> Hi
>
> Due to an unfortunate oversight of an incorrect branch merge a couple of months
> ago, a recently backported security fix caused an unwanted gdal soname bump in
> F37, due to an update from the 3.5.x series to the 3.6.x series.
>
> I'm preparing a gdal-3.6.2-8.really3.5.3.fc37 to address this, please don't
> rebuild any dependencies in the meantime, as the new package will bring back
> the previous soname.
>
> Apologies for the troubles.
Hello,
this is not the first time I saw a bodhi update that breaks dozens of
dependencies, goes unnoticed for a week and is automatically pushed stable,
only to discover many packages fail to install.
How come we don't have an automatic check for this? What can be done?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
5 months, 2 weeks
