Files
fm-orchestrator/tests/integration/example.test.env.yaml
Hunor Csomortáni b41b6b9cc1 Tests: allow reusing an existing module build
Module builds take a long time to run, which can be a pain to wait for
during integration test development.

Instead of requiring developers to locally tweak the test code to be
able to reuse module builds, allow specifying the build ID of the module
build to be reused in test.env.yaml .

Signed-off-by: Hunor Csomortáni <csomh@redhat.com>
2019-11-20 14:27:33 +01:00

35 lines
1.2 KiB
YAML

---
packaging_utility: fedpkg
# API endpoint of the MBS instance under test.
mbs_api: https://mbs.fedoraproject.org/module-build-service/2/module-builds/
# Git instance used by the build system.
git_url: https://src.fedoraproject.org/
# Koji instance the MBS instance under test communicates with.
koji:
server: https://koji.fedoraproject.org/kojihub
topurl: https://kojipkgs.fedoraproject.org/
# Test data to be used by the tests.
# Items in here are mapped by their name to the tests that use them.
# For example test_scratch_build will use scratch_build.
testdata:
scratch_build:
# MBS build id to be reused for this test.
# When specified no new build is started for this test,
# but the existing one reused.
build_id: 1234
# Name of the module.
module: testmodule
# Branch which is going to be built for this test.
branch: scratch-build-branch
failed_build:
module: testmodule
branch: failed-build-branch
# Batch considered by this test.
batch: 2
# List of components expected to fail in the batch.
failing_components:
- comp1
# List of components expected to complete or canceled in the batch.
canceled_components:
- comp2