Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 318.1
edited by Carlijn Kokkeler
on 2023/12/21 14:49
on 2023/12/21 14:49
Change comment:
There is no comment for this version
To version 304.1
edited by Carlijn Kokkeler
on 2023/12/21 13:51
on 2023/12/21 13:51
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,7 +5,12 @@ 5 5 6 6 **Hi there, eMagiz developers!** 7 7 8 -== **Overviews and logging** == 8 +== **TBD** == 9 + 10 + 11 + 12 +== **Feedback Items** == 13 + 9 9 //__Runtime overview__// 10 10 We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 11 11 ... ... @@ -16,48 +16,27 @@ 16 16 17 17 [[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 18 18 19 -//__Runtime restart or redeploy overview__// 20 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 21 - 22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 23 - 24 -//__Missing log entries__// 25 -We improved crash handling so that log messages clearly show when and why a container failed to start. 26 - 27 -//__Runtime logging__// 28 -We fixed a bug where no new log messages were showing up, even though they were produced by the container. 29 - 30 -== **Feedback Items** == 31 - 32 - 33 33 //__Breaking changes pop-up__// 34 34 Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 35 35 36 36 [[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 37 37 38 -//__External recipients emailaddress__// 39 -The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 40 - 41 41 //__Broker queue metrics dashboards__// 42 42 It is now possible to select the MQTT broker in the queue metrics dashboards. 43 43 44 -//__Runtime image version__// 45 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 46 - 47 - 48 48 == **Bug Fixes** == 49 49 50 -//__ Message throughput__//51 - Themessage throughputgraph intheManage phasewillnow showthecorrectdata,independent fromtheselectedtime internal.Before,thisgraphwouldnotshow anydatain somecases.34 +//__Deployment execution error message__// 35 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup. 52 52 53 53 //__Cloud template upgrade unjust rollback__// 54 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 38 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 55 55 56 -//__ Nextgeneration block__//57 - Apply toenvironmentwillnowbeblockedwhentrying todeployGen3runtimesonaGen2model.40 +//__Missing log entries__// 41 +We improved crash handling so that log messages clearly show when and why a container failed to start. 58 58 59 -//__ Deploymentexecution errormessage__//60 - In somecases when a machinetype step in thedeploymentplanexecutionerrors, theportal may giveanerrorwhentrying to display theerrormessage. Thishas beenfixed by nowshowingageneric error in the deployment plan and logging thefull error intheDeployhistory. TheDeploy history will show a summary of theerror andshowthefull error messageina new pop-up.43 +//__Runtime logging__// 44 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 61 61 62 62 == **Fancy Forum Answers** == 63 63