Scheduled CI: test the installer and test suite on new distribution releases
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the platform functions in utils/install_openrvdas.sh (get_os_type, check_os_supported, install_prereqs, find_python) and the container-test approach used in #716. Review OPERATIONS.md §5 for the installer limitations this workflow must complement, then design the scheduled GitHub Actions matrix around the listed images and the venv, pip install -e ., pytest test/, and manage.py migrate steps. Done means a weekly/manual workflow exists, reports the resolved release and failing step in a new or existing issue, and keeps non-blocking rolling images separate from pinned floors.
Written by the indexing model from the issue text.
Description
Problem
Linux distributions release on their own schedules, and nothing tells us when one does, or whether OpenRVDAS still installs and runs on it. As of October 2026 the installer refuses Ubuntu 26.04 LTS (released April 2026) and Ubuntu 26.10 (October 2026) as unknown versions, and nobody noticed for six months. Both ship Python 3.14, which nothing in OpenRVDAS had been tested on. OPERATIONS.md §5 notes that the installer's correctness "lives in environments no CI job reproduces".
The installer is being changed to accept new releases above a per-distribution floor rather than keep an allow-list. That change fixes the refusals, but it means a new release is accepted without ever having been tried. This issue is about finding out promptly when a new release breaks something.
Proposal
Add a scheduled GitHub Actions workflow, run weekly and on demand, with a matrix of container images on moving tags. In each container it would:
- Run the installer's own platform functions, unchanged:
get_os_type,check_os_supported,install_prereqsandfind_python. They can be extracted fromutils/install_openrvdas.shthe way the #716 container tests did. - Build a venv with the chosen interpreter and run
pip install -e .. - Run
pytest test/andmanage.py migrateagainst the platform's own SQLite.
Suggested matrix:
| Image | Why |
|---|---|
ubuntu:latest, ubuntu:rolling |
Picks up each new LTS and interim release the week it ships |
ubuntu:devel |
Months of warning before an Ubuntu release (non-blocking) |
debian:stable |
Picks up each new Debian release |
debian:testing |
Warning before the next Debian release (non-blocking) |
almalinux:latest (or rockylinux/rockylinux:latest) |
Picks up each new RHEL-family release |
Pinned oldest supported: ubuntu:22.04, debian:12, almalinux:9 |
Keeps the floors honest |
When a job fails, the workflow opens an issue, or comments on an open one, naming the image, the release it resolved to (from /etc/os-release) and the failing step.
Optionally: a step querying the endoflife.date API for ubuntu, debian, rhel, almalinux and rocky-linux would flag when the oldest supported release passes end of life. That's the signal to raise a floor in the installer.
Not covered
Containers can't exercise supervisord, nginx, systemd or serial hardware, so this complements real-machine testing of the installer rather than replacing it.
- Dominant language
- Python
- Stars
- 57
- Forks
- 30
- Avg merge
- 3h 14m
- Merged PRs (30d)
- 56
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OceanDataTools/openrvdas
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
OceanDataTools/openrvdas#760 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
OceanDataTools/openrvdas#758 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
OceanDataTools/openrvdas#748 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 58/100
OceanDataTools/openrvdas#743 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 54/100
OceanDataTools/openrvdas#717 ·
Maintainers usually reply within 1 day
All issues in OceanDataTools/openrvdas
Similar issues
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
almanac-data/climate-almanac#138 ·
Maintainers usually reply within 1 day
-
level/subtask type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wazuh/wazuh-virtual-machines#1091 ·
Maintainers usually reply within 1 day
-
Python: Bug: ChatMessageContent.from_element drops AudioContent and BinaryContent into raw TextContentPossibly taken @halcyon-past claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/semantic-kernel#14824 · 1 comment ·
Maintainers usually reply within 3 days
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#142 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LedgerHQ/app-bitcoin-legacy#306 ·