Wiki source code of 210 - Deployment Delights

Version 166.1 by Carlijn Kokkeler on 2023/12/04 15:52

Hide last authors
Carlijn Kokkeler 157.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.
eMagiz 1.1 2
Carlijn Kokkeler 165.1 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
Erik Bakker 35.1 4
Carlijn Kokkeler 155.1 5 =====New features=====
Carlijn Kokkeler 150.1 6
Carlijn Kokkeler 166.1 7 * Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
Carlijn Kokkeler 156.1 8
Carlijn Kokkeler 109.1 9 =====Minor changes=====
Erik Bakker 93.1 10
Carlijn Kokkeler 166.1 11 * Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 * Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
Erik Bakker 93.1 13
Carlijn Kokkeler 159.1 14 ====Bug fixes====
Carlijn Kokkeler 155.1 15
Carlijn Kokkeler 166.1 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.
18 * Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 * Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 * Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 * Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 * Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
Carlijn Kokkeler 158.1 23
Erik Bakker 101.1 24