ci(qualification): test DEB and RPM installation profiles
@elezar is already working on this.
Since Sep 18, 2026.
Assessment
This issue has not been assessed yet.
Description
Description
Define the qualification policy for OpenShell installation profiles and add package-manager profiles for DEB and RPM candidate artifacts.
The policy keeps responsibilities explicit:
- scenarios configure the machine and runtime environment;
- installation profiles install and verify OpenShell;
- testsuites verify post-install behavior and stateful transitions.
The DEB and RPM profiles must install the exact candidate packages through the guest's native package manager and compose with the same scenarios and testsuites used by native installation.
Context
- Parent release pipeline: #2860
- Native-install proof-of-concept pipeline: #2976
- Completed reusable clean-install work: #2974
- Installation profile model: #3419
- N-to-N+1 upgrade testsuite: #2975
- Release policy: RFC-0014
The native profile establishes the proof-of-concept pipeline. Package installation is separate qualification work and is a prerequisite for package-based upgrade testing.
Definition of Done
- The installation-profile policy documents ownership, inputs, outputs, lifecycle, verification, diagnostics, and cleanup boundaries.
- A DEB profile installs candidate packages on Ubuntu 24.04 through the native package manager.
- An RPM profile installs candidate packages on Fedora through the native package manager.
- Both profiles consume immutable candidate artifacts without rebuilding or using floating
devartifacts. - Both profiles verify installed package versions, candidate identity, expected services, and gateway health before a testsuite runs.
- Native, DEB, and RPM installations can run the same independently selected testsuite without scenario-specific forks.
- Failures retain package-manager, systemd, gateway, and scenario diagnostics without secrets.
- Documentation explains how to add another installation profile under the same policy.
- N-to-N+1 upgrade behavior remains in #2975 rather than being embedded in an installation profile.
Out of Scope
- N-to-N+1 upgrade behavior
- Helm, Homebrew, Snap, MSI, and WinGet installation profiles
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 271
Contributor 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 NVIDIA/OpenShell
-
area:docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:cli state:validated
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
state:triage-needed
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
area:build spike state:review-ready state:stale
Difficulty 2/5 Half a day Newbie friendliness 68/100
All issues in NVIDIA/OpenShell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100