Changes for page 256 - Power Up
Last modified by Erik Bakker on 2025/11/04 12:44
From version 281.1
edited by Erik Bakker
on 2025/09/21 21:29
on 2025/09/21 21:29
Change comment:
There is no comment for this version
To version 167.1
edited by CarlijnKokkeler
on 2023/12/04 15:54
on 2023/12/04 15:54
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 53-RinceRepeat1 +210 - Deployment Delights - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,21 +1,24 @@ 1 - This release featuresvariousupdatestoourplatform,witha user-centricfocus,asweworkonwrapping up improvedfunctionality forourneweventstreamingbroker.All thoseimprovementswillbeshared in thefuture onceeverythingisready.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>> doc:Main.Release Information.Release Blogs.253-RinceRepeat.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 -==== MajorChanges====5 +=====New features===== 6 6 7 -* Deploy - >Containers:Theusercannow easily see the containersa flow should run on in Deploy → Containersvia the button in theflow grid. Furthermore, we haveoverhauledthe userexperience onthisoverviewtoalignwith recentimprovementstoother partsof Deploy.(#976)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. 8 8 9 -==== Minor changes====9 +=====Minor changes===== 10 10 11 -* When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push. ** 12 -* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message. 13 -** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]] 14 -* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment. 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. 15 15 16 -==== Bug fixes====14 +====Bug fixes==== 17 17 18 -* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702) 19 -* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703) 20 -* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706) 21 -* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652) 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. 23 + 24 +