particle-os/debian-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge/test/data
History
Tomáš Hozza b8e1450a35 stages/mkdir: add exist_ok option to not fail if directory exists 
Add a new optional stage option to not fail if the specified directory
already exists. This will make it easier to support creation of custom
repositories via customizations in osbuild-composer. The reason is that
if a specified directory exists in an image, because it was created by
an RPM, then creating it would fail. However, the user may have
specified different mode for the directory, than it already has. Since
there is no way to know for sure if the directory already exists on the
image, without building the image itself, it is desired to handle this
case gracefully as valid in specific use cases.

The default behavior stays the same - specifying an existing directory
path will lead to an error.

Signed-off-by: Tomáš Hozza <thozza@redhat.com>
2023-01-16 20:19:27 +01:00
..
manifests test/data: set source epoch for certain pipelines 2022-12-15 13:10:35 +00:00
os-release test: update test manifests to use Fedora 34 2021-06-07 12:15:26 +02:00
scripts osbuild: run isort on all files 2022-09-12 13:32:51 +02:00
sources sources/ostree: set contenturl when pulling from remote 2022-10-14 12:04:54 +02:00
stages stages/mkdir: add exist_ok option to not fail if directory exists 2023-01-16 20:19:27 +01:00
README.md test: rename mpp-*.json to *.mpp.json 2020-10-19 17:37:46 +01:00
v2 test: Add skopeo tests 2022-02-10 14:43:17 +01: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 fedora prefix is used for manifests that are kept up to date to the newest fedora release, and thus do not expose a specific f30, f32, etc. behavior.

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

    The filesystem manifest is used to test assemblers. These tests doesn't need a big filesystem tree representing a whole operating system. Instead, this manifest's tree is constructed just from the filesystem package and is marked using the selinux stage.

    Manifests ending on .mpp.json are fed through the ManifestPreProcessors and then stored in the same directory with an .json extension (replacing .mpp.json). generated files are committed to the repository. Nevertheless, if you need to regenerate them, use make test-data.

  • ./sources/: This directory contains test-data for runtime tests of the source-engines. It contains a directory that is served via HTTP in the tests, and a directory of test-cases what to expect when using the attached sources.json.

  • scripts: This directory contains scripts used from other tests, i.e. although they are executables they are at the same time test-data to the actual (unit) tests.