On Fri, Feb 28, 2020 at 10:06:18AM +0100, Jan Pazdziora wrote:
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.
Checking the
https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenki...
the rpms well pulled in from the package-specific repo
swid-tools.noarch 0.8.9-1.fc32 @test-swid-tools
So it seems like the gating tests don't have to wait for the updates-testing push and some other message could be used.