Build unmerged APKs on pull request #8044

jonnyandrew · 2023-01-31T13:52:39Z

Type of change

Feature
Bugfix
Technical
Other :

Content

When building APKs for pull requests, build from the unmerged source.

Note that test jobs continue to build from merged source in order to reduce the chance of breaking the CI after merging.

Motivation and context

When testers test unmerged features built from pull requests, they should expect to test the same code that developers are working on in their development branch.
Repeated builds of the same PR branch should result in the same binary.

CI logs

From the build of 9f10c49

Checking out the ref
  /usr/bin/git checkout --progress --force 9f10c49bd8f6571fc470c2bae974f97aafb9717b

  HEAD is now at 9f10c49 Build unmerged APKs on pull request
/usr/bin/git log -1 --format='%H'
'9f10c49bd8f6571fc470c2bae974f97aafb9717b'

Tests

N/A

Tested devices

N/A

Checklist

Changes has been tested on an Android device or Android emulator with API 21
UI change has been tested on both light and dark themes
Accessibility has been taken into account. See https://github.com/vector-im/element-android/blob/develop/CONTRIBUTING.md#accessibility
Pull request is based on the develop branch
Pull request includes a new file under ./changelog.d. See https://github.com/vector-im/element-android/blob/develop/CONTRIBUTING.md#changelog
Pull request includes screenshots or videos if containing UI changes
Pull request includes a sign off
You've made a self review of your PR
If you have modified the screen flow, or added new screens to the application, you have updated the test UiAllScreensSanityTest.allScreensTest()