On Mon, May 10, 2021 at 11:04 AM David Sterba dsterba@suse.com wrote:
Hi,
btrfs-progs version 5.12 have been released.
Notable things:
[...]
- travis-ci integration has been disabled, I'd like to find another hosted CI but so far none provides a recent kernel so more tests won't pass, last option is to self-host some VMs and monitor git, getting just build tests works but we need to run the testsuite
This is unfortunate. However, I've been noodling around the idea of asking the Fedora CI folks if we could add upstream CI using Fedora on VMs. I guess now is as good of a time as any...
Aleksandra, are there any resources we could use to wire up btrfs-progs against Fedora latest stable and Rawhide across architectures so the code could be continually tested as changes are landed? There's that fancy Zuul instance[1] that might be useful here.
[1]: https://softwarefactory-project.io/zuul/tenants
-- 真実はいつも一つ!/ Always, there's only one truth!
Hi, Neal,
On Mon, May 10, 2021 at 8:50 PM Neal Gompa ngompa13@gmail.com wrote:
On Mon, May 10, 2021 at 11:04 AM David Sterba dsterba@suse.com wrote:
Hi,
btrfs-progs version 5.12 have been released.
Notable things:
[...]
- travis-ci integration has been disabled, I'd like to find another hosted CI but so far none provides a recent kernel so more tests won't pass, last option is to self-host some VMs and monitor git, getting just build tests works but we need to run the testsuite
This is unfortunate. However, I've been noodling around the idea of asking the Fedora CI folks if we could add upstream CI using Fedora on VMs. I guess now is as good of a time as any...
Aleksandra, are there any resources we could use to wire up btrfs-progs against Fedora latest stable and Rawhide across architectures so the code could be continually tested as changes are landed? There's that fancy Zuul instance[1] that might be useful here.
I suggest that you talk with the Packit team.
Packit provides Packit As a Service [1] approach to test upstream changes packaged on top of the latest Fedora or CentOS Stream environment. For example you can use it on GitHub by enabling the Packit GitHub App for you repository and adding the rpm spec file in the repo.
Afaik Packit can run tests not only on containers but also on virtual machines. So it is technically possible to run more complex scenarios which require latest Fedora kernel.
CC'ed Tomas Tomecheck from Packit.
[1] https://packit.dev/docs/packit-as-a-service/
Hi! Aleksandra, thanks for the ping.
This is correct, packit project provides capabilities similar to Fedora CI directly in your upstream repository - via tight GitHub integration. The builds are happening in Fedora COPR and tests are running in fresh VMs on AWS: you can have fedora stable, rawhide, epel, centos-stream.
Here is a guide how to start: https://packit.dev/docs/packit-as-a-service/
We hang out in #packit freenode channel and are happy to help you to set things up.
Cheers,
Tomas
On Tue, May 11, 2021 at 4:09 PM Aleksandra Fedorova alpha@bookwar.info wrote:
Hi, Neal,
On Mon, May 10, 2021 at 8:50 PM Neal Gompa ngompa13@gmail.com wrote:
On Mon, May 10, 2021 at 11:04 AM David Sterba dsterba@suse.com wrote:
Hi,
btrfs-progs version 5.12 have been released.
Notable things:
[...]
- travis-ci integration has been disabled, I'd like to find another hosted CI but so far none provides a recent kernel so more tests won't pass, last option is to self-host some VMs and monitor git, getting just build tests works but we need to run the testsuite
This is unfortunate. However, I've been noodling around the idea of asking the Fedora CI folks if we could add upstream CI using Fedora on VMs. I guess now is as good of a time as any...
Aleksandra, are there any resources we could use to wire up btrfs-progs against Fedora latest stable and Rawhide across architectures so the code could be continually tested as changes are landed? There's that fancy Zuul instance[1] that might be useful here.
I suggest that you talk with the Packit team.
Packit provides Packit As a Service [1] approach to test upstream changes packaged on top of the latest Fedora or CentOS Stream environment. For example you can use it on GitHub by enabling the Packit GitHub App for you repository and adding the rpm spec file in the repo.
Afaik Packit can run tests not only on containers but also on virtual machines. So it is technically possible to run more complex scenarios which require latest Fedora kernel.
CC'ed Tomas Tomecheck from Packit.
[1] https://packit.dev/docs/packit-as-a-service/
-- Aleksandra Fedorova bookwar