CI May 2020

ci@lists.stg.fedoraproject.org

3 participants
4 discussions

[CI][gating.yaml] Test names starting with org.centos.prod.ci.pipeline.. are deprecated
by Aleksandra Fedorova 21 May '20

21 May '20

1 0

Jenkins Outage Resolved
by Jim Bair 19 May '20

19 May '20

A heads up that we encountered an issue this morning (US time) with our Jenkins instance: https://pagure.io/fedora-infrastructure/issue/8926 Restarting and relocating Jenkins within the openshift cluster solved our NFS cluster - I also restarted a handful of failures that I could find, but then jobs starting rolling in, so I left Jenkins to do it's thing. If any tests or jobs are missing from the NFS outage, restarting the job should resume and run as expected. If not, please let us know in #fedora-ci on freenode. -Jim

1 0

Adding OpenID To Jenkins Tomorrow
by Jim Bair 13 May '20

13 May '20

I wanted to send out a note that tomorrow, we will be adding OpenID support to our jenkins instance for Fedora to allow for FAS ID Logins. We don't expect any downtime with the change, but if we accidentally lock ourselves out (always a possibility), we may need to reboot/make changes to recover. If that happens, we'll ensure any missed tests get triggered as expected. -Jim

1 0

'symlinks' inspection now in rpminspect
by David Cantrell 07 May '20

07 May '20

The issue filed: https://github.com/rpminspect/rpminspect/issues/133 I bumped up priority on this one to get something usable for Fedora CI and others quickly. The 'symlinks' inspection is now present. Here's what it does: * Checks all symlinks present in the 'after' build. If you are comparing two builds, that's the second build. If you are just running rpminspect against a single build, it's that build. * For each symlink found: - Read the destination and see if it exists in any subpackage in the build. If it does not exist, report the dangling symlink as VERIFY - For symlinks with too many levels of redirection (ELOOP), report it as dangling with the strerror() output on ELOOP as the details. - If a symlink found was a directory in the before build, report this change as BAD. This is a limitation of rpm and we want rpminspect to guard against packages doing it. - If any non-directory in the before build became a symlink in the after build, report that as a VERIFY. And that's about it. The trick here is that we permit symlink source and destinations to span subpackages, so we cannot rely on readlink(3) and realpath(3) in the code. Absolute symlinks are easy enough to deal with, but what I do for relative symlinks is manually resolve the destination. I have tested what I am doing with things like ncurses builds and debuginfo packages and things with lots of symlinks and everything is resolving correctly. Valgrind reports 0 bytes lost. Hooray! WHAT I NEED FROM YOU: * Please test the latest rpminspect available in Copr: https://copr.fedorainfracloud.org/coprs/dcantrell/rpminspect/ * You can reduce what inspections rpminspect runs with the -T option, so you could do: rpminspect -T symlinks NVR * Run single build inspections but also build comparisons. Use Koji build NVRs and rpminspect will fetch them. * Report problems on the rpminspect Github project page. Please open new issues rather than piling on to a single issue. It makes things easier for me. Thanks, -- David Cantrell <dcantrell(a)redhat.com> Red Hat, Inc. | Boston, MA | EST5EDT

1 0

2024

2023

2022

2021

2020

2019

2018

2017

CI May 2020