Changes for page 210 - Deployment Delights
Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 162.1
edited by Carlijn Kokkeler
on 2023/11/22 15:02
on 2023/11/22 15:02
Change comment:
There is no comment for this version
To version 165.1
edited by Carlijn Kokkeler
on 2023/12/04 15:30
on 2023/12/04 15:30
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -20 9-Max Verstappen1 +210 - Deployment Delights - Content
-
... ... @@ -1,6 +1,6 @@ 1 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 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.20 9-Max Verstappen.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]]. 4 4 5 5 =====New features===== 6 6 ... ... @@ -11,7 +11,6 @@ 11 11 =====Minor changes===== 12 12 13 13 * Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 14 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 15 15 * Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. 16 16 * Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server. 17 17 ... ... @@ -18,16 +18,12 @@ 18 18 ====Bug fixes==== 19 19 20 20 * Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas. 21 -* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 22 22 * Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. 23 23 * Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture. 24 24 25 -====Infra and image changes==== 26 26 27 -* Infra: New logging feature enabling us to make better choices in encryption standards. 28 28 29 29 30 30 31 31 32 32 33 -