Work out remaining CI/CD issues #90

Closed
opened 2018-04-30 21:54:26 +02:00 by tzarebczan · 1 comment
tzarebczan commented 2018-04-30 21:54:26 +02:00 (Migrated from github.com)

The Issue

Ensure that latest apk builds show up on build.lbry.io/github and Playstore + potentially for all commits on build page (the app side does this).

Notes from Slack:

Jeremy I'd propose making a proper CI/CD process relatively high priority for mobile. We're going to need a relatively simple process to ship + deploy new app, so any longer processes we're using currently are effectively wasting some effort.


shockr 4 days ago

I already have a release build script done. The minor challenge I have is making sure that the built release is the same as the Play Store release, because Google Play also signs the APK. But it's a non-issue if we're fine with having 2 differently signed APKs (One for the Google Play Store, and the other generated by the build script).

shockr 4 days ago

I'll need to investigate if there's an API for publishing APKs to or downloading published APKs from the Play Store.

System Configuration

  • Device:
  • Android version:

Anything Else

Screenshots

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. We are also available on live chat at https://chat.lbry.io --> ## The Issue Ensure that latest apk builds show up on build.lbry.io/github and Playstore + potentially for all commits on build page (the app side does this). Notes from Slack: ``` Jeremy I'd propose making a proper CI/CD process relatively high priority for mobile. We're going to need a relatively simple process to ship + deploy new app, so any longer processes we're using currently are effectively wasting some effort. shockr 4 days ago I already have a release build script done. The minor challenge I have is making sure that the built release is the same as the Play Store release, because Google Play also signs the APK. But it's a non-issue if we're fine with having 2 differently signed APKs (One for the Google Play Store, and the other generated by the build script). shockr 4 days ago I'll need to investigate if there's an API for publishing APKs to or downloading published APKs from the Play Store. ``` ## System Configuration - Device: - Android version: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->
akinwale commented 2018-05-09 20:45:26 +02:00 (Migrated from github.com)

Done.

Done.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-android#90
No description provided.