eclipse-sailing-analytics/sailing-analytics
1
0 Fork 0
mirror of https://github.com/eclipse-sailing-analytics/sailing-analytics.git synced 2026-11-02 01:00:46 +00:00
Code Activity

further details for MoMa handling for Android app builds

Browse Source
This commit is contained in:
Axel Uhl committed 2026-09-30 20:42:45 +02:00
1 parent fe19925dbd
commit 27653b7e6e
1 file changed
+5 -1
Download Patch File Download Diff File Expand all files Collapse all files
wiki/info/landscape/building-and-deploying.md
+5 -1
View File
@@ -124,7 +124,11 @@ Our points of contact for the Hyperspace / Azure Pipeline migration are Marc Bor
### Running a Build / Release / Promote Cycle
To release the apps, go to the MoMa records of the two apps ([https://moma.devint.net.sap/#/apps/124](https://moma.devint.net.sap/#/apps/124) and [https://moma.devint.net.sap/#/apps/123](https://moma.devint.net.sap/#/apps/123)) and from there into the Assembly-Data and press the "Add Release" button. Make sure the "Build System" is set to "free - Hyperspace Azure Pipelines". Make sure you set the "Is this build to be uploaded to Google Play Store (after manual approval)?" field to "Yes - directly to Google Play (General Availability)" in case you have tested you apps already and are sure they can be uploaded to the public store. Otherwise, select "Yes - but to Google Closed Track first (with option for GA afterwards)" which will upload to the Google Closed Track store first, so you can test the apps once more prior to publication. In this case you'll have to resume or reject the "Manual Validation" step (GP Prod Deploy?) after your tests. Then run the ``configuration/releaseAndroidApps.sh`` script, like this:
To release the apps, go to the MoMa records of the two apps ([https://moma.devint.net.sap/#/apps/124](https://moma.devint.net.sap/#/apps/124) and [https://moma.devint.net.sap/#/apps/123](https://moma.devint.net.sap/#/apps/123)) and from there into the Assembly-Data and press the "Add Release" button. Make sure the "Build System" is set to "free - Hyperspace Azure Pipelines". Make sure you set the "Is this build to be uploaded to Google Play Store (after manual approval)?" field to "Yes - directly to Google Play (General Availability)" in case you have tested you apps already and are sure they can be uploaded to the public store. Otherwise, select "Yes - but to Google Closed Track first (with option for GA afterwards)" which will upload to the Google Closed Track store first, so you can test the apps once more prior to publication. In this case you'll have to resume or reject the "Manual Validation" step (GP Prod Deploy?) after your tests.
From the MoMa entries, then also use "Add Release" in each app's "Google Play Metadata" tab. Select "Patch (3rd digit)" for the App Release Version and enter useful data into the "Release Notes" section. Confirm your ECCN classification further down below on the page and save. Then approve the metadata and write the e-mail to naming@sap.com for Brand Voice approvals for the release notes texts. Once this approval has been granted (you will be informed by e-mail), send the Release Notes to LX Labs for translation using the "Send to LX Lab" button.
Only then run the ``configuration/releaseAndroidApps.sh`` script, like this:
```
./configuration/releaseAndroidApps.sh