Skip to Content

Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51
From version 261.1
edited by Erik Bakker
on 2025/06/05 09:53
Change comment: Renamed back-links.
To version 170.1
edited by Carlijn Kokkeler
on 2023/12/08 09:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -246 - Preparation Paradise
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,24 @@
1 -In our previous release, we released functionality to increase the stability of Windows runtimes. This time, we followed that up by adding additional safety measures on the runtime level. Additionally, we have several pieces now available to prepare for pending changes to our event streaming offering. Furthermore, we introduced several minor improvements to the platform.
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 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.246 - Preparation Paradise.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 -==== Minor Changes ====
5 +=====New features=====
6 6  
7 -* Deploy - General: Updated the Java arguments applied to Windows containers to align with the container limits, thereby improving the stability of these containers.
8 -* General - Runtime: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V332.WebHome||target="blank"]] is available.
9 -** This adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
10 -** This updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
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 of the release in the Deploy phase.
11 11  
12 -==== Bug fixes ====
9 +=====Minor changes=====
13 13  
14 -* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
15 -* Manage - Error Messages: The non-working download button for payload content files now displays a more descriptive error message text. (#886)
16 -* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
17 -* Q&A Forum - General: You will no longer receive an email notification about your comments on posts in the Q&A forum. (#1462)
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.
13 +
14 +====Bug fixes====
15 +
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)
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.
23 +
24 +