Commit graph

16 commits

Author SHA1 Message Date
Marc Durdin
a1c8e63cc8 chore(android): cleanup Android build scripts and artifact filenames
* Specify clearer filenames for Android samples and test KeyboardHarness
* Cleanup android/*/build.sh to match current patterns
* Remove obsolete jcenter dependency
* Export BUILDER_CONFIGURATION in builder.inc.sh

Fixes: #16137
Fixes: #16181
Test-bot: skip
Build-bot: skip release:android
2026-07-13 16:36:29 +02:00
Eberhard Beilharz
4d81589f48
maint(common): use unique names for Keyman version variables
Previously the builder scripts defined a readonly `VERSION` environment
variable for the Keyman version. That caused problems when another
(external) script tried to define a `VERSION` variable. We encountered
this problem when trying to move the TC build steps of a configuration
into a single script (#13399) when we tried to source `~/.nvm/nvm.sh`.

This change uses a Keyman specific prefix for the version variables and
renames `VERSION` → `KEYMAN_VERSION` etc. Unfortunately these variables
are used in a lot of places, so this turned out to be a bit of a yak
shave.

Test-bot: skip
2025-05-07 18:46:51 +02:00
Darcy Wong
d2030767c7 refactor(android/app): Update Gradle for final apk name 2023-02-27 11:46:05 +07:00
Marc Durdin
fc4eb2b2c8 chore: address review comments 2023-01-23 14:13:38 +07:00
Marc Durdin
067028cec2 chore: revise tag variable name to VERSION_GIT_TAG
Introduce new $VERSION_GIT_TAG environment variable, and update all
references to release@version in all projects to use the new variable.
2023-01-21 17:02:50 +07:00
Marc Durdin
971e8db53c fix(android): bump version_code major calculation
Version code is, for 17.1.33: 1810033. This supports up to 9999
builds for a given major.minor version. We only support up to 9 minor
versions for a given major version but at present we are not using
minor versions at all.

Despite this calculation, the version_code should be treated as an
opaque integer, used only for Play Store publishing.

NOTE: accidental publish of beta 17.0.6 during 16.0 beta cycle has
forced a version_major bump, which is a permanent change. Relates to
issue #7705.
2022-11-17 05:40:42 +11:00
Darcy Wong
ea45ab7177 fix(android/app): Update use of tag and environment 2022-11-11 13:40:25 +07:00
Darcy Wong
8824678567 fix(android/app): Avoid calling build-utils again 2022-11-10 16:14:04 +07:00
Darcy Wong
a0f546471f chore(android/app): Revert version.gradle
Keep build-utils code to just KMAPro so it doesn't affect FV Android
2022-11-10 15:27:29 +07:00
Darcy Wong
81588c9448 fix(android): Fail version.gradle on exception 2022-11-10 15:03:16 +07:00
Darcy Wong
52d45de605 fix(android/app): Use build-utils to populate build info 2022-11-10 14:45:03 +07:00
Darcy Wong
9645a6c11c fix(android/app): Add tier to version.gradle 2022-11-10 11:23:31 +07:00
Marc Durdin
9798f86b16 chore(android): rework versionCode system
We now generate a versionCode directly from the release version number,
and this is what we use for Google Play Store to ensure that we have
an always-incrementing version number.
2020-12-15 06:31:01 +11:00
Darcy Wong
fe09ac73fe fix(android/app): Fix environment portion of app version string
When displaying the Info page of alpha builds from the Play Store, we noticed the version string displayed the wrong environment:
`14.0.X-alpha-local` (CI builds should have ended with `-alpha`).

It turns out  the `VERSION_` shell variables  from `build-utils.sh` aren't visible in `version.gradle` (though CI environment variables like `build_counter` are visible).

This PR:
* Exports the two VERSION strings needed in version.gradle
* Updates the Info page to simply display `BuildConfig.VERSION_NAME`
2020-08-06 10:34:26 +07:00
Marc Durdin
b5f32fbbaf fix(android): use environment and version-with-tag for sentry 2020-04-28 11:34:22 +10:00
Marc Durdin
742aee39d7 chore(android): use new version infrastructure 2020-01-29 08:55:19 +11:00