CI for builds with musl

[antonialoytorrens]

To test new kernels from here, I have to compile them every time on my computer before testing anything. My computer is not fast, and it may take hours to compile and test a single kernel build.

To work around that, I'm using a custom version of Debian on my TF101.
Nevertheless, for easier installation, automation and deployment, PostmarketOS is far better and more recommended for these devices.

Is it possible to add an extra CI implementation with musl (from Alpine Linux latest)?

[okias]

I'm pretty sure it's not about the Alpine.

First, the generated kernel (which we currently build) is libc agnostic, so you can run it on Debian, pmOS, or any distro you can find.

Second, would be nice to have something like pre-generated .apk package from our buildsystem, but that's probably job for someone who wants it really badly 😉

You can find builds here: https://github.com/grate-driver/linux/releases

Edit: my workflow was usually:

1. build old kernel
2. export it into /tmp/postmarketos (or how it's called) with pmbootstrap export
3. replace the kernel with abootimg
4. upload with fastboot

sadly it only works, when you don't change modules or version (which change dependency on modules version).

[digetx]

Kernel image itself indeed doesn't use libc. Are you asking about automating the .apk packaging, like @okias suggested, or something else?

[antonialoytorrens]

Kernel image itself indeed doesn't use libc. Are you asking about automating the .apk packaging, like @okias suggested, or something else?

Yes, it would be great to automate the .apk packaging.

[antonialoytorrens]

sadly it only works, when you don't change modules or version (which change dependency on modules version).

Oh, maybe that's the reason that it does not work straightforward for me on PostmarketOS.