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
Hi Jan,
On Wed, Nov 22, 2023 at 9:44 AM Jan Kaluža jkaluza@redhat.com wrote:
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
Can you please share light what is the large maintenance needed in these tests? They are fairly stable right now, there is no much development in them ongoing.
As these tests will be still used, afaict, for CentOS Stream, where will those be maintained?
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.
My team is already taking over the Fedora CI Jenkins deployment, but we are surprised these tests cannot be maintained together with CentOS Stream. Can you explain how is that possible, as basically those tests do the same (maybe against different koji instanaces)? Are you planning to have different tests?
Will rpmdeplint and rpminspect cease to work Fedora?
Thanks for clearing up these questions.
Best regards, /M
Thank you for understanding, Jan Kaluza -- _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
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.
I have some updates here. I received feedback from various people and teams during the last few days (thanks for that, because it actually allows us to see who the real users of these non-blocking tests are) and it seems we might be able to keep the mentioned gating tests running in the current "maintenance" mode and maybe also improve them later next year once we finish with another project the team is currently working on. The decision does not depend only on me, so I'm not going to promise anything *right now*, but I wanted to give you an update that we might find a way forward without dropping these tests. I will keep you informed in this thread.
Regards, Jan Kaluza
Thank you for understanding, Jan Kaluza