Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 316.1
edited by Carlijn Kokkeler
on 2023/12/21 14:43
Change comment: There is no comment for this version
To version 318.1
edited by Carlijn Kokkeler
on 2023/12/21 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,12 +5,7 @@
5 5  
6 6  **Hi there, eMagiz developers!**
7 7  
8 -== **TBD** ==
9 -
10 -
11 -
12 -== **Feedback Items** ==
13 -
8 +== **Overviews and logging** ==
14 14  //__Runtime overview__//
15 15  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.
16 16  
... ... @@ -21,6 +21,20 @@
21 21  
22 22  [[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
23 23  
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 +
24 24  //__Breaking changes pop-up__//
25 25  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'.
26 26  
... ... @@ -35,11 +35,7 @@
35 35  //__Runtime image version__//
36 36  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.
37 37  
38 -//__Runtime restart or redeploy overview__//
39 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
42 -
43 43  == **Bug Fixes** ==
44 44  
45 45  //__Message throughput__//
... ... @@ -46,14 +46,8 @@
46 46  The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
47 47  
48 48  //__Cloud template upgrade unjust rollback__//
49 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
54 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
50 50  
51 -//__Missing log entries__//
52 -We improved crash handling so that log messages clearly show when and why a container failed to start.
53 -
54 -//__Runtime logging__//
55 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
56 -
57 57  //__Next generation block__//
58 58  Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
59 59