Docker automatic builder for Android APK's. Note that the Android Studio SDK is only supports Intel/AMD64 platform!
With APKautobuild you can build .APK installer files directly from Git code on any system supporting Docker. No need to install Android Studio or SDK's.
Docker is supported for multiple platforms (Intel/AMD64 only):
* Windows 10/11 (Command or WSL2)
* Apple Mac Pro
* Ubuntu/Linux (intel)
System requirements:
Memory available: 12GB or more
Docker memory available: at least 8GB
Internet connection is required for pulling remote Docker image
To build an Android APK using Docker you need to (see configuration):
* Install Docker Desktop
* Clone this project
* Setup your keystore at data/**keystore**
* Edit the configuration file data/**asbuilder.config**
* Build the .APK by running ./build_APK.sh (Windows: build_APK.cmd)
Optionally you can define muliple build configurations using multiple "data" locations: The data directory is defined in the config.build file through the BUILDENV parameter (default is "./data")
The Windows Subsystem for Linux lets developers run a GNU/Linux environment.
-- including most command-line tools, utilities, and applications
-- directly on Windows, unmodified, without the overhead of a traditional virtual machine or dual-boot setup.
https://docs.microsoft.com/en-us/windows/wsl/install
Docker Desktop for Windows is the Community version of Docker for Microsoft Windows. You can download Docker Desktop for Windows from Docker Hub.
https://docs.docker.com/docker-for-windows/install/
or
https://www.docker.com/products/docker-desktop
Open a terminal session on your Windows (command prompt), Windows/WSL2 or Mac Pro. Next, create a base directory and clone the code form Github:
mkdir /android
cd /android
git clone https://github.com/vanelsberg/APKautobuild.git .
cd APKautobuild
To build the .APK file you need to:
* Setup your keystore at data/**keystore**
* Edit the configuration file data/**asbuilder.config**
On startup the docker countainer mounts a data directory for storing configuration data and build results:
* data/keystore:
Must contain theh folowing files:
appkeyAndroidAPK-keystore.jks
ks-password
* data/output:
Must contain the following files:
appkeyAndroidAPK-keystore.jks -> personal keystore
ks-password -> password file
The documentation uses the above defaults for keystore and password filenames. Optionally change the default keystore and password files throug ediiting the configuration file.
Configuration is in the file aapsbuilder.config:
-
data/keystore/ks-password
To sign .APK's after building you need to configuare the keystore- and key password for your keystore file:
Create a plaintext password file named ks-password containing 2 lines (see ks-password.sample):
- line1: keystore password
- line2: key password
-
data/keystore/appkeyAndroidAPK-keystore.jks
To sign your .APK installer files you need to copy your Android keystore file named appkeyAndroidAPK-keystore.jks to the location /data/keystore.
Remark:
You can use a keystore generated from Android Studio or generate a new keystore file using the Docker autobuilder. Make sure to define your password in the ks-password file, then run:
./generate-keystore.shThe above prompts you for "Distinguished Name" fields for your key. It then generates a new keystore file. The key generated is valid for 10,000 days.
Note that you can only update an APK with a new version that was signed with the same key. When generating a new keystore make sure you uninstall the APK first before installing the new version build bij autobuild!
-
data/asbuilder.config
This file contains the following configuration items. You may need to update them for your specific build.
-
Git config variables:
GIT_PROJECT Projectname GIT_REPO Git repo clone url GIT_BRANCH Git branch to build (e.g: "dev","master" - empty="master") GIT_COMMIT Git commit hash to build (empty=latest commit) GIT_MERGE_PRNUM Git PR number to merge with current branch/commit (e.g: "3347,3357,3362" or empty) -
Signing keyfile, alias and password files:
KEY_FILE KEY_ALIAS KEY_PASSW_FILE
-
-
Other configuration:
- The script file dbrun.sh defines a variable named data_local. It defaults to the directory data in the root directory of this project but you may change this to any directory location on your local machine.
Once your configuration is setup you can build your APK.
On initial run docker will need to download a docker image to the local docker image repository. The image is sized at about 1GB so, depending on your internet connection, this may take some time. Once the image is loaded succesive runs will start without downloading.
To build on Linux run the following commands:
chmod u+x build_APK.sh # Make the script executable
./build_APK.sh --clean # Run the script to build from scratch
./build_APK.sh --rebuild # Run the script to build with new/updated code from Git
./build_APK.sh # Run the script to rebuild using previous build result
You will find the build output in the location data/output
To build on Windows run the command batch file:
build_APK.cmd
* **Important**:
When editing the _aapsbuilder.config configuration file make sure not to change the file line ending from Unix 'LF' to Windows 'CR/LF'.
You can check by opening the file with Windows notepad.exe (enable the status bar from view) at look at the bottum-right of the window: it should say "Unix (LF), UTF-8"
You will find the build output in the location data/builds
On first run Docker needs to download the APKbuilder image from the Docker repository. Depending on the speed of your internet connection this may take some time. Subsequent builds however will reused the image downloaded locally.
An active internet connection is required while building the APK for getting the latest code and libraries to build the APK's
20240521 * Updated this README * Updated to docker images theod00r/apkbuilder:1.1.10 * Added asconfig parameter 'GIT_MERGE_PRNUM' for optionally PR merging