Open robinpaulson opened 4 years ago
My initial attempts can be seen here, commented out: https://github.com/martykan/forecastie/blob/master/.github/workflows/android.yml
Specifically i don't know the name or location of the apk produced by the build process. Apart from that I think the workflow is fine.
Modified from this: https://github.com/actions/upload-artifact
Initially arm7(?), later perhaps for more architectures.
Most of the process is now working, still some problems with locating the apk after it has been built. Do check the .yml file if you'd like to help.
Done, in a slightly manual way. Check the releases page for a compiled arm binary. I'll try to get it working automatically.
I tried the built apk today... it won't install. More investigation needed, the device was Replicant 6.
I've been investigating the CI/CD capabilities built into Github's new "Actions" tool. At the moment we are using it for testing, to see if code changes break the code base.
I'd like to add a new workflow which automatically builds the latest code and makes an apk available here on Github.
It's certainly possible, there are a variety of template workflows available, but I'm struggling with some aspects of it, specifically where the build process stores the .apk. Any help or suggestions welcome.