On Wed, Jan 06, 2021 at 07:27:54AM -0800, Tom Stellard wrote:
On 1/6/21 5:39 AM, Miro Hrončok wrote:
> On 06. 01. 21 14:25, Pierre-Yves Chibon wrote:
> > On Wed, Jan 06, 2021 at 01:20:26PM +0000, Fabien Boucher wrote:
> > > Hi,
> > >
> > > I'd like to introduce a recent change to Fedora Zuul CI.
> > >
> > > Some packagers raised the need to get CI feedback for builds on
> > > supported
> > > architectures.
> > >
> > > So we have defined in Zuul some jobs that can be configured to
> > > be triggered
> > > at PR's creation and update.
> > >
> > > rpm-scratch-build-aarch64
> > > rpm-scratch-build-armhfp
> > > rpm-scratch-build-i386
> > > rpm-scratch-build-ppc64le
> > > rpm-scratch-build-s390x
> >
> > If we configure these to run for every single PR opened on dist-git,
> > could we
> > then retire simple-koji-ci?
> > (Or should we merge simple-koji-ci into a zuul-based CI?)
>
> In the future, possibly.
>
> The problem now is that you need to opt in for this and it does not know
> how to recognize a noarch package yet. So if we enable this for all
> packages, we would waste resources (I mean, it is certainly a good idea
> to verify a noarch package builds on all architectures, but not sure if
> all the time).
>
Can we disable simple-koji-ci for packages with zuul enabled? Currently,
when I create a PR for LLVM, it triggers 3 scratch builds (simple-koji-ci,
zuul, CI tests), and this seems unnecessary to me.
Not currently, there is a reason that simple-koji-ci starts with "simple" ;-)
Pierre