This setup is no longer needed since: - The current build system and GPU backend integration have been restructured. - CI now works with the virglrenderer crate. - Environment variable overrides are no longer necessary to avoid CI failures. Signed-off-by: Dorinda Bassey <dbassey@redhat.com> |
||
|---|---|---|
| .. | ||
| main-tests.json | ||
| README.md | ||
| staging-tests.json | ||
buildkite custom pipelines
This folder contains the custom pipelines for this repository.
If we add a new pipeline we need to enable it in https://buildkite.com/rust-vmm/vhost-device-ci/steps
Custom pipelines currently defined are:
-
main-tests.jsonThis is based onrust-vmm-ci/.buildkite/test_description.json. We have an internal version, because we have several applications that have dependencies that don't work very well on musl, so it's easier to manage CI by having our own internal pipeline. -
staging-tests.jsonThis is based onmain-tests.json. We should keepstaging-tests.jsonaligned with it as much as possible to make sure we don't notice any difference in CI when we move a crate from the staging to the main workspace.