I know you are probably swamped with other things, but could you please elaborate on whether this is something you eventually plan to do, or not?

@churchyard We still haven't resolved the infrastructure question as described in the linked issue.

Our immediate plans include the update of the Fedora CI Jenkins and refactoring of the pipelines, bringing those from Taskotron to that new Jenkins setup.

The work is happening under https://github.com/fedora-ci

I think we should defer the EPEL testing topic till we get the set of generic tests working for Fedora Rawhide

So, eventually, yes, but not soon. Correct?

So, eventually, yes, but not soon. Correct?

Yes.

But I wonder what Zuul team thinks about EPEL pull-requests.

@fbo Is it possible to support epel8, with centos8 as a base image, on Zuul?

@bookwar yes it should be possible. We have the centos8 image available on Zuul then the rest should be pretty similar than fedora 30/31/32/master branches. I'll request a epel8 branch for one project, and add the epel8 branch support in fedora-zuul-jobs. Then I'll run a test.

@bookwar I've done the required setup and validated that jobs trigger on the epel8 branch of rpms/python-gear 1. The rpm-test job is configured to run on a centos-8 node with epel-release package installed.

It means, now, Zuul is configured to run the jobs on epel8 branch for projects attached to Zuul.

A Zuul run on epel8 here: https://src.fedoraproject.org/rpms/python-tox/pull-request/18#comment-39292

And it worked, thank you.