ci: Use just recipes for all tests
justfile: Add compose-dry-run recipe
To use in CI to perform dependency resolution for all official variants.
ci: Perform dependency resolution for all variants
ci: Reformat package lists
Import GitLab CI config
This config is not used in Fedora infra (see .zuul.yaml instead) but is used for testing in https://gitlab.com/fedora/ostree/ci-test.
.zuul.yaml
Importing it here makes synchronizing changes accross the repos easier.
Co-authored by: Alexej Kowalew 616b2f@gmail.com
Zuul: Unify all jobs to save on CI costs
We need a VM for both the compose-dry-run and the compose-base tests thus to avoid spawning two VMs in Zuul, let's keep everything in a single job to save money.
Holding as we are in beta freeze
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/67750307896b4e579aef9d4df3de63a1
2 new commits added
zuul: Use Fedora 40 container & cloud images
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/4935703050a747e9bb26578baf3f9719
+ rpm-ostree compose tree --unified-core --repo=repo --dry-run fedora-silverblue.yaml bwrap: Creating new namespace failed: Operation not permitted
Hum, why is this failing here but not in rawhide?
recheck
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/7189f912d64646d18a2f191ecd6c71f5
6 new commits added
zuul: Use F39 container & F40 cloud image
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/5b1269e050b54175a1428d963a4d6f8d
Rawhide ran the test in a VM as the containers are broken so maybe we can not run this test in a container.
https://pagure.io/workstation-ostree-config/pull-request/493
rebased onto 55cb8289b2a6670b92ba34d4f1c3f349c7a3de2d
I think you probably could run that test in a container, but it would need to be a somewhat-privileged container to allow it to run bwrap, and I don't think the current zuul setup makes it possible to get a job run in a privileged container. At least on a quick poke through https://pagure.io/fedora-project-config . I think it can only create unprivileged containers.
bwrap
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/d306a6148b17470eb11a1e3cfeabaea0
5 new commits added
ci: Split dependency check and run checks all on failures
ci: Fix yaml lint
ci/validate: Also validate Zuul YAML config
zuul: Fix YAML indentation
justfile: Run compose-dry-run for a single variant
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/0e540152f3844109b90041ca723b9131
rebased onto c3824402a278b46baa51ca577a3ccf37b7c082f4
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/2891b61b38584b9f8d2dd1ed471d5915
rebased onto fa400b436ca3871e3c31cd0dc7ca1026a478e99c
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/687d1ecb76dd48f7afb572abb909d4e1
Pull-Request has been merged by siosm
ci: Use just recipes for all tests
justfile: Add compose-dry-run recipe
To use in CI to perform dependency resolution for all official variants.
ci: Perform dependency resolution for all variants
ci: Reformat package lists
Import GitLab CI config
This config is not used in Fedora infra (see
.zuul.yamlinstead) butis used for testing in https://gitlab.com/fedora/ostree/ci-test.
Importing it here makes synchronizing changes accross the repos easier.
Co-authored by: Alexej Kowalew 616b2f@gmail.com
Zuul: Unify all jobs to save on CI costs
We need a VM for both the compose-dry-run and the compose-base tests
thus to avoid spawning two VMs in Zuul, let's keep everything in a
single job to save money.