On Feb 16 16:46, Attila Darazs wrote:
Dear CentOS CI Team & CI users,
We run quite a few jobs on the CentOS CI system and it's an essential part for testing our libvirt deployment style of TripleO Quickstart.
With the recent Jenkins security update our jobs broke[1] while requesting nodes with the cico client. It was easy to fix, however it made us think about the advantage of using a single job scheduler for all our testing.
Upstream OpenStack infra is now completely based on Zuul v3[2] without having Jenkins as a backend for running jobs. Soon the same thing is going to happen to our rdoproject.org instance as the new version of SoftwareFactory[3] contains the v3 version, and we're considering replacing our downstream jobs with Zuul based ones as well.
It would be an obvious advantage for us in the long term if we could unify the way we handle job running and configuration through Zuul instead of Jenkins.
I just wanted to test the waters with regards to the CentOS CI team's willingness to consider setting up an instance and the other users interest in it.
Please let me know what you think.
Best regards, Attila
[1] https://bugs.launchpad.net/tripleo/+bug/1749845 [2] https://docs.openstack.org/infra/zuul/ [3] https://softwarefactory-project.io/docs/main_components.html _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
At this point we're focusing our efforts in ci.centos.org on Jenkins.
I don't want to discourage any PoC/exploratory work, but it's out of scope to do a large scale migration to another execution engine right now.
--Brian