chris/musicshare
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Faster Android builds: ccache, Gradle build cache, 64-bit only, no release lint

Browse Source 
Most of a build was compiling the same C++ twice per APK with nothing reused between builds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011Y2iUsKEWDuRGjK5FPmcUP
This commit is contained in:
chris
2026-10-15 15:21:35 -04:00
co-authored by Claude Opus 5.5
parent 0a26e33bfe
commit c7bd8f0ad3
5 changed files with 29 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ANDROID-CI.md
+5 -2
View File
@@ -20,8 +20,11 @@ The pieces:
## One-time setup (on the Gitea server)
The server needs about 8 GB of free memory during a build and about 15 GB of disk for the image and
caches. A first build takes 30-40 minutes; later ones reuse the Gradle cache.
The server needs about 8 GB of free memory during a build and about 20 GB of disk for the image and
caches. A first build takes 15-40 minutes depending on the machine; later ones reuse the Gradle build
cache and ccache's compiled C++ (volumes `musicshare-gradle` and `musicshare-ccache`) and take a few
minutes. The APKs are for 64-bit phones (`arm64-v8a`); set `ABIS=armeabi-v7a,arm64-v8a` in the workflow's
Build step to include old 32-bit ones.
The caches are Docker volumes, which live wherever Docker keeps its data (usually `/var/lib/docker`).
Check that disk has room (`df -h /var/lib/docker`): if it fills up, everything else using Docker on the
server, including databases, stops writing.