1.5.2 Release Notes
- Jacques Marais
- Former user (Deleted)
Owned by Jacques Marais
Functional requirements
- HD-1180 Ability to disable an app or an app release with a message to users
- HD-1070Â Introduce an ID shared between apps and app releasesÂ
Bug fixes
- HD-1212 Certain values for the text field "datatype" attribute has no effect
- HE-976 NDoH Change-log not returning (fixed by means of database optimization)
- HE-935 Jackson Service Loader Exception
Additional Information
HD-1070 introduces a shared identifier between apps and app releases. This is done by means of a app release group name.Â
The benefit provided by this feature is that it allows developers to only see releases for release groups used by them and therefore drastically reduces the risk of upgrading apps with unrelated and incompatible source code by accident.
The following should be noted:
- When releasing apps from the HeliumDev client, using the release command, you'll have to specify a release group name for your release. This can be done by specifying the value when prompted for it during the release process or by setting a default for all releases of a specific project. This is achieved by setting the releaseGroup variable in the HeliumDev client:
he-dev> project set releaseGroup=agri
- When creating new apps on the Helium core app, a "Release Group" now also needs to be provided
- When deploying snapshots, the release group name of "Snapshot" followed by a timestamp will automatically be used
- Current releases that are not snapshots will be updated with a release group name the same as the release name
- Current releases that are snapshots will be updated with a release group name of "Snapshot" followed by a timestamp
- When upgrading apps to a specific release, tags can be specified that filter releases based on their group names
- When upgrading apps to a specific release, you can edit a release's group name via the upgrade button adjoining 'Update' dropdown
Please see the updated documentation here for more information.
Â
BETA Deployment (RC) | 2017-04-06 |
---|---|
Production Deployment | 2017-04-13 22:00 CAT |