On Fri, Feb 28, 2020 at 09:20:16AM +0100, Pierre-Yves Chibon wrote:
> Depending on how the pipeline actually *does* testing of updates, you
> *may* be able to schedule on the update being created or edited
> instead/as well (this is how the openQA scheduler does it; we don't use
> the koji-build-group.build.complete topic at all, we use
> bodhi.update.request.testing (published when an update is created) and
> bodhi.update.edit (published when an update is edited) instead.
> However, you can only do that if the pipeline does not rely on the
> packages actually being in the updates-testing repo, but retrieves them
> itself. At the point those messages are published, the package files
> cannot be relied upon to be present anywhere outside of Koji.
Well, when the update is created the RPMs are signed yet and we want to test the
signed RPM to make sure that we test what is being pushed to the users.
From reading this, I think things work as designed, it's just that there were no
push to update-testing for F32 yet.
The question is, could the CI run based on some other messages, like
those that Adam mentioned? Will the test setup be able to pull the
bits from koji or does it rely on updates-testing? Bruno was able to
schedule the CI job for my Fedora 32 update and it passed so it looks
like it was able to get the bits in spite of no update-testing pushes
for Fedora 32.
In general it seems like a suboptimal user experience from maintainers'
point of view when they create an errata and there is an undefined
time for which the errata will show failing tests because the gating
tests haven't been even scheduled. Any change we can make to get the
erratas all ready (with tests run and passed) will increase the chance
that maintainers will be willing to add gating tests to their
packages.
--
Jan Pazdziora
Product Owner, Platform Security Readiness, Red Hat