Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/05/22 13:37

From version 167.1
edited by Carlijn Kokkeler
on 2023/12/04 15:54
Change comment: There is no comment for this version
To version 169.1
edited by Carlijn Kokkeler
on 2023/12/05 11:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -In the last sprint cycle, we focused on improving several aspects related to the deployments. It is now possible to see an overview of container versions, and containers will not be deployed and restarted when no changes have been made. Moreover, several bug fixes have been done, relating to the Flow Designer, the Deploy phase, and alerting.
1 +In the last sprint cycle, we focused on improving several aspects related to the deployments. It is now possible to see an overview of container versions, and containers will not be deployed and restarted when no changes have been made. Moreover, several bug fixes have been done relating to the Flow Designer, the Deploy phase, and alerting.
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.
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)
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.