osbuild / osbuild/image-builder
Test manifests with the minimum supported osbuild version
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 77
- Forks
- 103
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 53
Description
We should add a test that installs osbuild at the version tagged as the minimum supported in data/dependencies/osbuild/. We need to catch cases where new options are added, the commit in Schutzfile is updated, but the dependency isn't.
My idea for this test is to get the osbuild rpm built by the tag specified by the dependency version (if one was released already), generate test manifests, and osbuild --inspect them.
If the dependency points to an unreleased version of osbuild, the test should be skipped.
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.
Research direction
Start with the dependency version in data/dependencies/osbuild/ and the related commit in Schutzfile. Determine how to build or obtain the osbuild RPM for a released tag, then inspect the existing manifest-generation test entry points. Done means manifests are checked with osbuild --inspect at the minimum supported version, while unreleased dependency versions skip the test.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100