Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 159.1
edited by Carlijn Kokkeler
on 2023/11/21 12:50
Change comment: There is no comment for this version
To version 160.1
edited by Carlijn Kokkeler
on 2023/11/22 14:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,7 +10,7 @@
10 10  
11 11  =====Minor changes=====
12 12  
13 -* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
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 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.
... ... @@ -19,7 +19,7 @@
19 19  
20 20  * Create - Flow Designer: An issue has been fixed in the flow designer where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
21 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 -* Deploy - Deployment plan: We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped.
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 could not start, or logging, errors and metrics could not be seen in the portal for a model that has just migrated to the next generation architecture.
24 24  
25 25  ====Infra and image changes====