element-hq / element-hq/element-android

Move exodus to GitHub action, and analyse release version instead of debug version

Open
#6,306 1 comment 0 reactions 0 assignees View on GitHub
A-DevX Privacy T-Task z-CI
Dominant language
Kotlin
Stars
3.7k
Forks
917
PR merge metrics
No merged PRs in 30d

Description

Currently exodus check is performed by buildkite: https://github.com/matrix-org/pipelines/blob/master/element-android/pipeline.yml#L62 on release and debug version of the app.

This as to be done by GitHub Action now, and could later be removed from Buildkite pipeline. As a reminder, we keep Buildkite as a CI Backup for now, and it's still used to build the unsigned Gplay released version of the app.

Other things to change when implementing this issue:
- exodus should be run only on the `Release` build. On Debug build we can have other trackers, and this is fine (I think). This is blocking #6300, see https://github.com/vector-im/element-android/pull/6300#issuecomment-1155196809 .
- it means that GitHub action should build `Release` version of the app on every PR. Currently this is not the case, and this is a problem, since `Debug` builds can succeed and `Release` builds may fail. Some code/dependencies are different for both types.
- Bonus: it will fix this [TODO](https://github.com/vector-im/element-android/blob/main/.github/workflows/build.yml#L70)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.