test upcoming android releases #2927
Comments
|
There is no test build 7.16 for Android |
|
Can we make one with CI? Every new merge could be uploaded automatically. I'm sure there are people who'd happily opt in for beta testing. |
|
Yes, I plan to do this today. It is possible that I could require your
help. If yes - I'll Skype you
|
|
Sure, but don't know how could I help. :) |
|
Could it be possible to automatically generate an apk after every PR merge, in order to cut the waiting time for testing? |
|
Yes, it is exactly what I want to do
|
- Fix existing configuration of openssl and curl flag files for different Android configurations - Make openssl and curl build more silent This fixes #2927 Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
|
@AenBleidd In the PlayStore, we can create a beta channel. Can the Travis automatically upload to PlayStore the apk? |
|
I'm afraid, BOINC is already on Beta channel but I can be wrong. I'm not
sure whether Travis can upload on PlayStore or not, I need to check this
but as far as I know we need sign all before uploading it to PlayStore and
I'm not sure that private keys are stored on GitHub.
@brevilo, @davidpanderson, can you please assist here?
|
|
The latest BOINC on PlayStore is not on beta channel for sure. |
|
So then |
|
I'm not seeing it. |
|
I have 7.14.1 (ec993779be), last updated 9 Oct 2018 My opinion, is if you do this automatically, maybe it should be labeled as alpha and not beta |
|
Yes, I'm participating in beta testing on PlayStore and have this option
enabled
|
|
Sorry, I neither have specific knowledge on nor access to the Play Store. |
|
I'm reopening because the changes in #2936 only create an unsigned APK. Someone with the key needs to sign and upload this to the PlayStore. I'll keep this open to remind that person of it. |
|
Instructions for participating in alpha or beta builds via the Google Play store are available here: https://boinc.berkeley.edu/trac/wiki/AndroidBoincTesting (note at this time just sign up for Beta testing). Builds that get uploaded to the Beta version need to signed via the keys that @davidpanderson so once we have an APK that we want to beta test at a larger scope, we can provide it to David to upload. @davidpanderson - did you want to change to the "App Signing by Google Play" process outlined here: https://developer.android.com/studio/publish/app-signing#google-play-app-signing to make it easier for you to manage keys and approve apps into the store? |
|
#2936 is closed. |
|
@AenBleidd @adamradocz |
|
What do you mean by that? |
|
No other version was uploaded to PlayStore yet.
And as far as I know there is no plans to do this in next few weeks.
|
Hi @TheAspens , that sounds like a very interesting option for BOINC. It's a major hassle if the signing key is compromised as it will affect the end user's experience. Having a compromised upload key is still bad but it doesn't affect the end user at all, so that's a major plus. So, yes, please let's opt in to that! Also, not having effective access to the PlayStore is THE main obstacle for Android releases right now. All the pending "BOINC-stops-after-n-minutes" issues should be resolved as soon as we release ANY update, based on current |
|
Might be off-topic, was it by design to stop uploading new versions of Android client to https://boinc.berkeley.edu/dl/ ? |
|
I talked with @davidpanderson and he said that he needs someone (probably @AenBleidd @adamradocz or @brevilo ) to volunteer to be the "android build master" for this release. Once David starts the client release process for the 7.16 release he will send you an email letting you know that he needs a new build and you will do a build from the client release branch and send him the unsigned apk and he will sign and upload to the google play store for beta testing. You would also need to watch for Android bug reports from the beta testing and advise about the status of the Android release and its readiness to go live. Would one of @AenBleidd, @adamradocz or @brevilo let me know if you can do this for this release? Thanks! |
|
@TheAspens, I can do this. If @brevilo or @adamradocz want to be Android Build Master too I suggest to make an election. |
|
I for one am happy to support @AenBleidd and/or @adamradocz taking this on as you guys are effectively running the Android part of BOINC - and you're already doing a great job! |
|
I'm ok with @AenBleidd being the Android Build Master. |
|
It's not a good practice.
Only builds from release branch should be used for such purposes. This
could be automated too but anyway, because Master branch could be
potentially unstable.
|
|
We could do both. I'm in strong favor to start actual continuous integration. CI-building |
|
99% of CI builds are not related to Android at all so I don't think that we
should auto-sign and push such releases to Play Store. By the way, this
means that we should either use separate version for Android or make a lot
of small releases with build-number change only.
APKs are also created by CI on weekly basis from master but I don't think
that there would be a lot of people who wants to install APKs manually
|
Since you're replying to my post: I didn't mean to imply that. I only supported the idea of having automated CI builds of both branches. If that's already the case, good. Whether continuous deployment to the Play Store (of release branch continuous integration builds) could be useful is a separate discussion and mostly up to the Android build or release manager - you :-) |
|
A little off topic - does the feedback entered at Google Play BOINC Beta page ever get read? Or we, users have to directly report issue here at GitHub? Also, kindly answer KexyBiscuit question? I also in support for the automatic builds for each essential Android related PR merges... |
Not sure. From time to time I take a look there. I plan to walk through all of them after the release to update/create corresponding tickets here in GitHub
It is the best case, of course, but nobody forces you to do this @KexyBiscuit, I believe David just forgot to upload it
Please use weekly builds from here: |
|
Can BOINC have separate test build that does not overwrite current release build? Preferably that can sideload with the current release build? I don't want to lose all those ongoing tasks by uninstalling the current release build because incompatibilities just to test a new version (or self compiled one)... |
|
I do not understand if Android 7.16 https://github.com/BOINC/boinc/projects/17 is open or closed? |
|
Currently no new BOINC for Android release will appear on Play Store due to the restrictions from Google side. |
Is there any way to test upcoming android releases?
I want to download/test Client Release 7.16, since in Google Play only 7.14.1 is available
The text was updated successfully, but these errors were encountered: