Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 233.1
edited by Erik Bakker
on 2025/03/10 09:59
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
Title
... ... @@ -1,1 +1,1 @@
1 -240 - Spring Cleaning
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,13 +1,24 @@
1 -In the last sprint, we focused on tidying up our house to prepare for various cool things later this year. As a result, we have a series of improvements and bug fixes for you to enjoy.
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.240 - Spring Cleaning.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 -* Overall UI/UX: Alerts / Notifications now have an icon before the text to further emphasize the meaning.
8 -* Overall UI/UX: We have updated our badge, switch, and progress bar components.
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.
9 9  
9 +=====Minor changes=====
10 +
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 +
10 10  ====Bug fixes====
11 11  
12 -* Create - Flow Creation: We have changed the auto-creation behavior for entry gates. This means we now avoid creating functionality in these entry gates only relevant for flows running inside a Mendix app.
13 -* Create - Reset Infra: Infra flows for systems labeled as a "Mendix Connector" can now be reset once more under all circumstances, including when your model utilizes the code mapping functionality.
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 +