particle-os/debian-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge/test/data
History
David Rheinsberg 020e78d571 test: import build-pipelines 
Extend the `f32-base.json` manifest to use our F32 build-root. Use the
new mpp-import-pipeline preprocessor to include `f32-build.json` as
build-root.
2020-06-05 09:27:40 +02:00
..
manifests test: import build-pipelines 2020-06-05 09:27:40 +02:00
os-release test: convert os-release-tests to test-data 2020-05-13 14:26:05 +02:00
README.md test: add F32 manifests and a manifest-preprocessor 2020-05-20 18:54:38 +02:00

README.md

OSBuild Test Data

This directory contains data used by the osbuild test-suite. Since many formats do not allow comments, this file shortly describes their purpose.

Directories

  • ./os-release/: This directory is consumed by the unit-tests of the os-release parser. The directory contains example os-release files (see os-release(5)). Their directory name is the expected output of the parser.

  • ./manifests/: This directory contains osbuild manifests used throughout the test-suite.

    Manifests prefixed with f30, f31, etc. are manifests that produce fedora images. If they have base as part of their name, they include a base set of packages which we very loosely define as @core plus the packages our test-suite needs. If they have build as part of their name, they have a very restricted package set which includes just what is needed in a build-root for osbuild.

    The rhel prefix is used for Red Hat Enterprise Linux images. Since they are not available publicly, the test-suite usually skips them.

    Manifests prefixed with mpp-* are fed through the ManifestPreProcessors and then stored in the same directory with the mpp-* prefix dropped. The generated files are committed to the repository. Nevertheless, if you need to regenerate them, use make test-data.