-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Android Release Automation Workflow (#33)
* Setup signingConfigs with my keystore file. * Create release.yml script that will build apk file and do release everytime that is a push on the main branch. * Fix gradlew no permission error. * Use java 17 on script. * Use variables from github secrets. * decode google-services.json file * List output apk-s. and also upload the apk regardless it's name * add signing config on release build type. * update script to decode keystore file. * add logging for keystore existence * Add script to automatically release the app on github. Also add latest git commit hash to apk file name. * replace ghaction-create-release with actions/create-release * use gh to create release. * Trigger when new pushes are on appRelease branch. * parse json to get upload_url * instead of using --json to parse upload url. Make directly an api call. * Use personal github token. * define a valid tag name. * use github cli "gh" to upload release. * remove print upload url. * Trigger GitHub Actions * remove upload of apk when i create the release * Add more descriptive naming on steps. * Fetch latest commits as notes for release. * remove APK_PATH and APK_NAME_BASE and replace usage directly with respective values * Create new TAG for each release to get release notes (commits) from latest release to current release. * Use PERSONAL_GITHUB_TOKEN to give permission when pushing new tag. * Clone repo with PERSONAL_GITHUB_TOKEN. * Push NEW_TAG with PERSONAL_GITHUB_TOKEN Access. * Handle when there is the first release. * Use keystore properties from github when build is from CI. And load locally when build is not CI. * Change target branch. --------- Co-authored-by: Diar Gegaj <[email protected]>
- Loading branch information
Showing
2 changed files
with
60 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters