Skip to content
Last updated

Release Workflow

It is essential to ensure that micro web applications are thoroughly tested and stable before being deployed to production. A defined release process allows to minimize the risk of production issues and helps to streamline application development by establishing clear guidelines and procedures for testing and deployment.

Release Process

Following are the recommendations for MWA releases:

  • Introduce different Appflow distribution channels for development and production builds. For example, development builds can be assembled from the develop source repository branch and deployed to the develop distribution channel. All successful app builds will be automatically assigned to this channel and become available for the Live Update feature. It will allow propagating the latest web app builds to mobile devices and iterate quickly during the development phase. Development builds can also be connected to QA environments from partner and EGYM to use the latest data and features provided by backend systems

  • Stable app builds can also use the existing develop distribution channel. The main difference between development and stable builds can be that mobile apps that are used to host micro web applications can point to different environments/versions of backend environments that are connected to web and native apps. The Live Update feature can also be enabled here, to automatically fetch the latest builds by mobile app

  • For production candidate builds it is proposed to assemble the web application from the main branch of the MWA Git repository and use the preprod channel for distributing LiveUpdates. These builds will be prepared by the partner development team, integrated into the corresponding EGYM mobile app and connected to the production backend environment. It is recommended to keep Live Update enabled, to simplify the assembly of the mobile app and distribution of web app fixes to already installed applications

  • For production builds the web app distribution can be triggered manually. It can be done by assigning the production channel to the web app build that has been tested as the production release candidate and approved for release. Live Update will allow you to assemble mobile app builds and simplify distribution of the web app. Mobile app builds will be prepared by teams that own the particular integration and connected to production backend environments

  • Hotfixes will be handled similarly to production candidate builds. They will be tested separately and then distributed through the production distribution channel.

Previous page
Next page