On Wed, Mar 11, 2020 at 02:44:14PM +0100, Aleksandra Fedorova wrote:
### New test: rpminspect
There is a new rpminspect test running in Fedora Rawhide gating enabled by default for all packages in a non-blocking mode.
More details: https://github.com/rpminspect/rpminspect
Status: Ready to Use Contact: David Cantrell (dcantrell)
Hello,
I've checked random no-noarch rawhide build in Koji
https://koji.fedoraproject.org/koji/buildinfo?buildID=1478656
found its update in Bodhi
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ccc90fa0aa
but I don't see rpminspect among its tests. Is that expected?
Incidently I see fedora-ci.koji-build.rpminspect.static-analysis listed in my 12 days old errata
https://bodhi.fedoraproject.org/updates/FEDORA-2020-ed976e62df
but looking at the log
http://fedora-build-checks.apps.ci.centos.org/blue/rest/organizations/jenkin...
it's not quite clear with what options the check was run, or indeed, where the run-rpminspect.sh came from.
Is there a plan to make understanding what is being run and how easier, for example by linking the CI configs from koji and bodhi, so that the maintainer has a clear path for finding the information?
### Tests for pull-requests via Zuul
Zuul team has enabled Zuul CI engine to test Pagure pull requests.
This is about pull requests in the upstream projects, not about dist-git / src.fedoraproject.org pull requests, right?