search

adam900710 / btrfs-fuse

A read-only, license friendly, FUSE based btrfs implementation
Other
27 stars 4 forks source link

Add basic CI using GitHub Actions #5

Closed davide125 closed 3 years ago

davide125 commented 3 years ago

This should be enough to kick off a build on every commit and PR.

Conan-Kudo commented 3 years ago

@davide125 Perhaps you should make the CI test various distributions instead? For example, here's what I did for appx-util: https://github.com/OSInside/appx-util/blob/main/.github/workflows/main.yml

adam900710 commented 3 years ago

I'm not yet familiar enough to deploy a CI yet, nor the purposed CI is good enough.

The planned self-test will involve fsstress using kernel btrfs module, and fssum to verify both btrfs-fuse and kernel are reporting the same metadata/data. Thus it would require some CI systems with newer enough kernel, especially for the future extent-tree-v2 on-disk format change.

This would lead to the same problem of btrfs-progs, there isn't a good enough CI platform using newer kernels.

So I'm not in a rush to deploy a CI, and prefer to put the (hopefully small enough) burden to the contributors. Any sane contributor should definitely run build tests by themselves, at least for now.