Changes

Summary

  1. jobs/bodhi-trigger: report SUCCESS even for UNSTABLE builds (details)
  2. jobs/bodhi-trigger: respect `test-patterns: skip` (details)
  3. jobs/test-override: run `cosa fetch` with `--with-cosa-overrides` (details)
  4. jobs/bodhi-trigger: send failure notifications to Matrix (details)
  5. docs/hacking: Add matrix-webhook secret and use it in jobs/bodhi-trigger (details)
  6. jobs/bodhi-trigger: Add a link to blueoecean in the matrix message (details)
  7. hacking: fix matrix webhook env var (details)
  8. Jobs/bodhi-trigger update matrix message formatting (details)
  9. jobs/bodhi-trigger: also report test successes (details)
  10. jobs/bodhi-trigger: print raw JSON instead of parsed object (details)
  11. bodhi-testing: add kexec-tools and makedumpfile (details)
  12. jobs/test-override: respect env vars for stream (details)
  13. upstream-ci: test upstream kdump builds against FCOS (details)
Commit d08ce149e81e62bb5b849bb7b7aafd26cace36b8 by Jonathan Lebon
jobs/bodhi-trigger: report SUCCESS even for UNSTABLE builds

When a snoozed test expires, if it has the `warn: true` key on, we'll
start warning and that'll show up as an UNSTABLE build. These warnings
are more for test maintainers than for public consumption so don't
translate them to NEEDS_INSPECTION because that will block updates on
gated components.
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit 64056158000681523d9f2e8fcf8876324553fc7f by Jonathan Lebon
jobs/bodhi-trigger: respect `test-patterns: skip`

If a test pattern is marked as `skip`, then respect that. Don't force
`basic` to run in that case. The logic there was meant as a way to force
`basic` to always run *if* some other tests were also selected, not to
counteract `skip`.

Fixes 6c1f869 ("bodhi-testing.yaml: support specifying tests to run").
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit 6146f5a1d7a3bee87fb5ba2c0202d28cd6bc3290 by Joseph Marrero Corchado
jobs/test-override: run `cosa fetch` with `--with-cosa-overrides`

Otherwise, if the override we're testing is pulling in new
dependencies, we won't know to fetch them. This came up in
https://bodhi.fedoraproject.org/updates/FEDORA-2024-969f546f80 which is
adding a dep on `composefs`.

This also matches CI in the coreos/fedora-coreos-config repo.

(Aside: we've talked in the past about getting notified when new deps
are added and the previous behaviour coincidentally did that, but this
doesn't seem like the right place for it; we shouldn't block packages
from entering Fedora on that account. That check probably belongs in
`bump-lockfile` instead).
The file was modified jobs/test-override.Jenkinsfile (diff)
Commit 784d18d14958c0b391772da477c39073728fc8c9 by Jonathan Lebon
jobs/bodhi-trigger: send failure notifications to Matrix

This job is still relatively new. Push out failure notifications to
Matrix to increase visibility and make it easier to collaborate on
investigating issues.
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit 17b3879dbdc7b0452823f3df59b6653844177f4b by Jonathan Lebon
docs/hacking: Add matrix-webhook secret and use it in jobs/bodhi-trigger
The file was modified HACKING.md (diff)
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit 930794291aba54cf37747dcfcc3224079d379f60 by Jonathan Lebon
jobs/bodhi-trigger: Add a link to blueoecean in the matrix message
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
The file was modified HACKING.md (diff)
Commit 29885ebb6db209940a38ae546a0fba143c97c624 by Jean-Baptiste Trystram
hacking: fix matrix webhook env var

See https://github.com/coreos/coreos-ci/pull/55#discussion_r1633248050
The file was modified HACKING.md (diff)
Commit b38b8c79be06cf98018a1862c161b7ab69077279 by Jean-Baptiste Trystram
Jobs/bodhi-trigger update matrix message formatting

Also include a link to the bodhi advisory
Also use propper markdown formatting as
https://pagure.io/fedora-infrastructure/issue/12057 landed

Fixes #67
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit 322a6d481a3bda9e79171e0338fad2fe4592d350 by Jean-Baptiste Trystram
jobs/bodhi-trigger: also report test successes

Sometimes, Bodhi testing is broken for a few days if rawhide is in a
bad shape. Let's also have the test report successes so that it's easier
to tell when upstream testing have been fixed. It makes it more obvious
also when e.g. just a single run failed in a series of otherwise passing
runs.
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit c088dcc406170d2eee426505e33bcd7088bbb2cd by Dusty Mabe
jobs/bodhi-trigger: print raw JSON instead of parsed object

That makes it easier to copy/paste if we want to replay a job (currently
even replaying a fedmsg-triggered job will still ask you to input the
`CI_MESSAGE`).
The file was modified jobs/bodhi-trigger.Jenkinsfile (diff)
Commit ee4a162272ce0fe8e9963c0123732c9bbcedcc55 by Jonathan Lebon
bodhi-testing: add kexec-tools and makedumpfile

We need to also tests theses, as we need them to support kdump.
This would have caught https://github.com/coreos/fedora-coreos-tracker/issues/1813
The file was modified bodhi-testing.yaml (diff)
Commit 07a689d9a2731a1ad401232f9e29bff3bfd242ca by Dusty Mabe
jobs/test-override: respect env vars for stream

This matches what we do in the pipeline.

Motivated by wanting to get to the bottom of
https://github.com/coreos/fedora-coreos-tracker/issues/1796, which
happens often in the Bodhi tests.
The file was modified jobs/test-override.Jenkinsfile (diff)
Commit a7c9ca3a5d4421614c5a0ce7abace8a555b77065 by Jean-Baptiste Trystram
upstream-ci: test upstream kdump builds against FCOS

In an effort to reduce kdump issues, let's run our tests against their
upstream repo, to catch problems earlier.

See https://github.com/rhkdump/kdump-utils/pull/62
Also: https://issues.redhat.com/browse/RHEL-70438
The file was modified jobs/seed-github-ci.Jenkinsfile (diff)

Summary

  1. vars/kola: deprecate --basic-qemu-scenarios (details)
  2. vars/kola: Add support for skipping a list of kola tags (details)
  3. vars/checkoutToDir: fix checkout step syntax (details)
Commit ed73e059c647ebc91f069f673c5eb3f4003d7211 by Steven Presti
vars/kola: deprecate --basic-qemu-scenarios

The argument for --basic-qemu-scenarios has been deprecated.
Depending on the version of cosa, the tests that would be skipped by these args are
now formal kola tests. And to skip them you can use --denylist-test commands.

skipSecureBoot now translates to  --denylist-test *.uefi-secure
The file was modified vars/kola.groovy (diff)
Commit 954e0026f26f23152aa7e1b2fc3a2bb871f59103 by Jonathan Lebon
vars/kola: Add support for skipping a list of kola tags

Introduce a kola parameter to allow skipping a list of kola tags.
This is particularly useful when adding new streams to the pipeline.

xref: https://github.com/coreos/fedora-coreos-pipeline/pull/1008

Reference: https://github.com/coreos/fedora-coreos-pipeline/issues/1002
The file was modified vars/kola.groovy (diff)
Commit f6b43daa3ea886c62d521f2e73c7b54758aa3a20 by Jonathan Lebon
vars/checkoutToDir: fix checkout step syntax

The extensions object's syntax here is incorrect:

> WARNING: Unknown parameter(s) found for class type 'hudson.plugins.git.extensions.impl.RelativeTargetDirectory': recursiveSubmodules

The `recursiveSubmodules` option is part of another extension type we
need to add to the list.
The file was modified vars/checkoutToDir.groovy (diff)