On Wed, 28 Aug 2019 at 03:16, Mikolaj Izdebski <mizdebsk(a)redhat.com&gt; wrote: Can koschei be limited to a single architecture or does it need to build against all targets? I am worried about the number of s390 builds we may be adding. -- Stephen J Smoogen.

SJS> Can koschei be limited to a single architecture or does it need to SJS> build against all targets? I am worried about the number of s390 SJS> builds we may be adding. Currently it only does builds for aarch64, ppc64le and x86_64, so it does at least know how to avoid building on everything. In addition, it is pretty good about not submitting jobs without plenty of idle builders to handle them. Back when it was first being deployed, koschei did swam the s390x builders but that was fixed. And these days, s390x isn't really our slowest architecture. - J<

Based on feedback received I have just added "EPEL 8" and "EPEL 8 playground" collections to Koschei. For now only a single package is tracked in each collection - epel-release package, but are free to add more packages as needed. On Wed, Aug 28, 2019 at 9:15 AM Mikolaj Izdebski <mizdebsk(a)redhat.com&gt; wrote: > > Fedora infrastructure has been asked [1] to enable Koschei [2] for > EPEL 8. Would this be useful to anyone? If yes, which of build targets > (epel8-candidate, epel8-playground-candidate) should Koschei submit > scratch builds for? > > [1] https://pagure.io/fedora-infrastructure/issue/8099 > [2] https://fedoraproject.org/wiki/Koschei