What is the best way to transport a Fiori Mobile App between environments?

[MikeDoyle]

Does anyone have suggestions as to best practice for transport Fiori Mobile apps (from development to test to production)?

I plan to start by deploying the html5 application and portal site content to test. Then I will need to trigger a Fiori Mobile build, perhaps from Web IDE on the test sub account. Is there anyway to transport the app configuration (from Mobile Secure Cloud) from the dev sub account, or do I need to do that again from scratch, possible leading to discrepancies between the apps for the different environments?

I notice that the sub account ID/GUID is listed in files like .project.json. Another approach would be to move the whole app at file level using GIT, then just change the entries which refer to the dev sub account. Then this app could be deployed to the Fiori Launchpad site in test. Would this be a better approach?

The customer does not have a Continuous Integration (CI) set up

What has everyone else been doing? What would you recommend?

Thanks in advance for your assistance

[former_member226695]

Hi Mike,

Agree with Britt! There seems to be no automated process here.

My client uses Airwatch to distribute the apps.

Let's say, we have release latest build to QA:

• In my web-ide, i go into neo-app.json >> ensure the destination points to my QA box (say, GW)

Note: GW is a destination configured in Cockpit that points to QA-box here

• Export and upload the offline project zip to the Admin team
• Admin generates & distributes the build to Airwatch
• Testing team downloads & installs the latest build from Airwatch & starts testing it...

-Cheers, Sai

[MikeDoyle]

Thanks for you input Sai. Unfortunately we don't manage the devices so we need to make the app publicly available, through Mobile Place.