Changes for page 215 - Tiny Tales
Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 169.1
edited by Carlijn Kokkeler
on 2023/12/05 11:44
on 2023/12/05 11:44
Change comment:
There is no comment for this version
To version 166.1
edited by Carlijn Kokkeler
on 2023/12/04 15:52
on 2023/12/04 15:52
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,4 +1,4 @@ 1 -In the last sprint cycle, we focused on improving severalaspects relatedto the deployments.Itisnowpossible toseeoverviewofcontainerversions,andcontainerswillnot be deployedandrestartedwhennochangeshavebeen made. Moreover, several bugfixeshave beenonerelatingtotheFlowDesigner, the Deploy phase, and alerting.1 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes. 2 2 3 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]]. 4 4 ... ... @@ -14,7 +14,7 @@ 14 14 ====Bug fixes==== 15 15 16 16 * Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 17 -* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100)17 +* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. 18 18 * Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 19 19 * Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck. 20 20 * Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.