Repository navigation
Test the repository set-up on Rocky Linux and AlmaLinux 9 and 10 - #16
Merged
Merged
Conversation
The repository test installs azentrius-repository from the signed test repository on Rocky Linux and AlmaLinux 9 and 10 as well as on Fedora 43. Each RPM system imports the repository's real key first, as the README's set-up does.
This was referenced Oct 23, 2026
stefan-azentrius
added a commit
to Azentrius/cockpit-status-board
that referenced
this pull request
Oct 23, 2026
## What and why Status Board is to be supported fully on RHEL 9 and 10. The first step is to check the package on the RHEL rebuilds; so far the tests installed the `.rpm` on Fedora 43 only. - New job `install` (one job per system: Rocky Linux 9 and 10, AlmaLinux 9 and 10): the `.rpm` installed with the distribution's own Cockpit (its version is printed), `rpm -V`, the page's files, the metainfo and the license file, then the removal. - README: Supported systems and the install section name the systems, and the package repository's `dnf` set-up is tested there too (relies on Azentrius/packages#16). No Cockpit runs in these containers, so this does not make RHEL a tested system yet. That needs the end-to-end test in a VM, which comes next; on RHEL 10 it also has to cover the host switcher, which Red Hat lists as deprecated and off by default. The new job is not one of the required checks (`test`, `e2e`). ## How tested - The changed workflow parses (strict YAML check, no duplicate keys). - The new job runs in CI on this pull request. Nothing outside the workflow and the README changed, so `make check`, `make lint` and the end-to-end test are untouched. ## Checklist - [x] No new or changed texts - [x] The page, its calls and the status contract are unchanged - [x] No secrets, keys or real data - [x] No new source files
stefan-azentrius
added a commit
to Azentrius/cockpit-image-update-monitor
that referenced
this pull request
Oct 23, 2026
## What and why Image Update Monitor is to be supported fully on RHEL 9 and 10. The first step is to check the packages on the RHEL rebuilds as thoroughly as on Debian and Fedora. - Job `install`: AlmaLinux 9 and 10 next to Rocky Linux 9 and 10 (installed with the distribution's own dependencies, the helpers answer, skopeo installs the way the page does it, the status as root and as nobody, the removal). - Job `upgrade`: now a matrix with one job per system: Debian 13, Fedora 43, Rocky Linux 9 and 10, AlmaLinux 9 and 10. Each upgrades from the newest older release, checks the files against this build, keeps the data and removes the package. - README (Supported systems, the package repository row) and `docs/INTERNALS.md` name the systems. The repository row relies on Azentrius/packages#16, which tests the `dnf` set-up on Rocky Linux and AlmaLinux. No Cockpit, Docker or systemd runs in these containers, so this does not make RHEL a tested system yet. That needs the end-to-end test in a VM with SELinux, which comes next. ## How tested - The changed workflow parses (strict YAML check, no duplicate keys). - The new and changed jobs run in CI on this pull request. Nothing outside the workflow and the docs changed, so `make check`, `make lint` and the end-to-end tests are untouched. ## Checklist - [x] No new or changed texts - [x] No changed formats - [x] User-visible changes are described above (none: CI and docs only, no new version) - [x] No secrets, tokens or real server data - [x] No new source files
stefan-azentrius
added a commit
to Azentrius/cockpit-cronjobs
that referenced
this pull request
Oct 23, 2026
## What and why Cron Jobs is to be supported fully on RHEL 9 and 10. The first step is to check the package on the RHEL rebuilds; so far the tests installed the `.rpm` on Fedora 43 only. - New job `install` (one job per system: Rocky Linux 9 and 10, AlmaLinux 9 and 10): the `.rpm` installed with the distribution's own dependencies (the versions of `cockpit-bridge` and `cronie` are printed), `rpm -V`, the page's files, the status units, the status helper before a write (`none`) and after one (both files mode 644, schema 1), then the removal with the status files. - README: the install section and the known limits name the systems, and the package repository's `dnf` set-up is tested there too (relies on Azentrius/packages#16). No Cockpit, cron daemon or systemd runs in these containers, so this does not make RHEL a tested system yet. That needs the end-to-end test with cronie in a VM with SELinux, which comes next. The new job is not one of the required checks (`test`, `e2e`). ## How tested - The changed workflow parses (strict YAML check, no duplicate keys). - The new job runs in CI on this pull request. Nothing outside the workflow and the README changed, so `make check`, `make check-ui`, `make lint` and the end-to-end test are untouched. ## Checklist - [x] No new or changed texts - [x] No crontab writes, root scripts or formats changed - [x] User-visible changes are described above (none: CI and docs only, no new version) - [x] No secrets, tokens or real server data - [x] No new source files
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The add-ons are to be supported fully on RHEL 9 and 10, so the repository set-up has to work there, not only on Fedora.
testnow installsazentrius-repositoryfrom the signed test repository on Fedora 43, Rocky Linux 9 and 10 and AlmaLinux 9 and 10, each with its signature checked, and removes it again.repository/azentrius.asc), as the README's set-up does, so a key a system's rpm refuses would show here.No change to the package itself, so no new version.