-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release APKs #2493
Comments
So, you mean, automatically? :-) |
Yes, Travis can be set up to do this automatically. https://docs.travis-ci.com/user/deployment/releases I also found a nice little tutorial explaining the steps: http://szagurskii.com/blog/how-to-deploy-apk-to-github-releases-with-travis-ci/ |
Sounds good. AFAIK this would need to be set up by the person who deploys releases, right? I'll try to set that up when I have time. :) |
@misaochan If this is a bit tricky can we at least have the APKs along with the beta/prod releases that we do. It won't need any Travis setup. Whenever you push a new tag to Github, you will have to manually edit the tag to add the APK as well. Having this will help us fix #3311 as appetize requires a publicly accessible link of the APK to be available. |
Sure, I can do that. :) Remind me if I forget, please. |
Tip: Release APKs can be downloaded at https://f-droid.org/en/packages/fr.free.nrw.commons/ , see the "Download APK" link under each version, leading to for instance https://f-droid.org/repo/fr.free.nrw.commons_1036.apk The signature is different so you may have to uninstall previously installed versions, in that sense it can not really be used to test migrations. |
If there is any benefit with attaching the production APK to each release note, do let me know. I could do the same. There's no problem with that. |
Summary:
It would be great if we could maintain release APKs for any beta/prod release that we make. Right now, if I need to do an upgrade testing from say v2.8.0, I will have to check out that branch and build it locally to install it. It would be nice to maintain these APKs under Github releases.
https://github.com/commons-app/apps-android-commons/releases
The text was updated successfully, but these errors were encountered: