mirror of
https://github.com/netbirdio/android-client.git
synced 2026-09-23 09:30:52 -07:00
Zoltan Papp
1d40d8f095
Reworks the Android UI, and brings over features the desktop client already had.
61 lines
3.0 KiB
Markdown
61 lines
3.0 KiB
Markdown
# Android client build and versioning
|
|
|
|
## The three workflows
|
|
|
|
### `build-debug.yml` — the CI gate
|
|
|
|
Runs automatically on every pull request and on every push to `main`. It has
|
|
three jobs: `build-debug` produces the AAR and a debug APK/AAB, then
|
|
`unit-tests` and `instrumented-tests` download that AAR and run against it, the
|
|
latter on an emulator.
|
|
|
|
Its product is a pass/fail signal, plus the `netbird-aar` artifact that the two
|
|
test jobs consume. The debug APK it uploads is a convenience for humans; nothing
|
|
in CI reads it.
|
|
|
|
### `build-release.yml` — the published release
|
|
|
|
Triggered by `release: published`, which fires for pre-releases too. It builds
|
|
the signed APK and AAB and attaches them to the GitHub release. This is the
|
|
source of anything that goes to the Play Store.
|
|
|
|
Release candidates run through this workflow: they are ordinary GitHub
|
|
pre-releases tagged `vX.Y.Z-rc.N` (for example `v0.6.0-rc.1`, `v0.3.3-rc.2`).
|
|
|
|
### `build-snapshot.yml` — the hand-distributed build
|
|
|
|
Manually dispatched. Produces a release-signed build from an arbitrary untagged
|
|
commit, uploaded as a 14-day artifact rather than published. The version name
|
|
anchors that commit to the last release it descends from, so a build off the
|
|
`v0.6.0-rc.1` line reads `v0.6.0-rc.1-snapshot-4d10386`.
|
|
|
|
Use it when someone needs a real, installable build of work in progress and you
|
|
do not want a public pre-release for it. Every run consumes a version code from
|
|
the shared counter, so it is not something to run per pull request.
|
|
|
|
---
|
|
|
|
## Differences
|
|
|
|
| | `build-debug` | `build-release` | `build-snapshot` |
|
|
|---|---|---|---|
|
|
| Trigger | `pull_request`, `push` → `main` | `release: published` | `workflow_dispatch` |
|
|
| Build type | debug | release | release |
|
|
| **Version name** | `ci-<sha>` | the release tag verbatim (`v0.5.0`, `v0.6.0-rc.1`) | `<tag>-snapshot-<sha>` |
|
|
| **Version code** | `9999` (fallback from `version.properties`) | `release_runs + snapshot_runs + 40` | `release_runs + snapshot_runs + 40` |
|
|
| **Signing key** | default Android debug keystore | Play upload keystore (`gplay.keystore`) | Play upload keystore (`gplay.keystore`) |
|
|
| **Firebase Crashlytics + Analytics** | **absent** | present | present |
|
|
| Runs tests | yes (unit + instrumented) | no | no |
|
|
| Artifact | `debug-artifacts-<name>`, 3 days; `netbird-aar`, 1 day | attached to the GitHub release | `<tag>-snapshot-<sha>`, 14 days |
|
|
| Permissions | `contents: read` | `contents: write`, `actions: read` | `contents: read`, `actions: read` |
|
|
| Concurrency group | none | `android-version-code-lock` | `android-version-code-lock` |
|
|
|
|
`<sha>` is the short commit hash of the `android-client` repository, not of the
|
|
submodule.
|
|
|
|
`<tag>` is the nearest release tag in the built commit's ancestry, as reported by
|
|
`git describe --tags --abbrev=0` — the closest tag walking back through the
|
|
commit graph, not the most recent tag by date. A branch that forked before a tag
|
|
was cut therefore reports the older tag, and merging `main` into it moves the
|
|
name forward.
|