Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
on 2023/12/18 12:20
Change comment:
There is no comment for this version
To version 288.1
edited by Carlijn Kokkeler
on 2023/12/06 08:59
on 2023/12/06 08:59
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 1-Log Luminary1 +210 - Deployment Delights - Content
-
... ... @@ -3,26 +3,25 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 6 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving. 7 7 8 -== ** TBD** ==8 +== **Alerts** == 9 9 10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives. 10 10 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 11 11 12 12 == **Feedback Items** == 13 13 14 -//__Missing properties overview__// 15 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 16 - 17 -ADD FIGURE 18 - 19 19 //__Container version overview__// 20 -D uetotheimproved build process for containers, therelease versionsand containerversionswillnotlongerbe thesameanymore.Therefore we introduce a way whereyoucan look up to see which container versionsare linkedto a specificrelease. This canhelpyou toidentifyifyourcontainers that are running have therightversionaccordingto the release.19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 21 21 22 22 [[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 23 23 24 -//__ Improveddeploymentprocess__//25 - Theimprovedrelease buildprocess, as mentionedabove,brings anothermajorimprovement to the platform. Because containerversionswill notbe updatedregularly wecanidentify during a deploymentwhichcontainershouldgeta newcontainer version.Onlytheones that shouldget a new version will be deployedandrestarted,allothercontainers will notgo down and keeprunning. Thisdecreases the deploymenttimeandimproveshe performance.23 +//__Unchanged containers__// 24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 26 26 27 27 //__Rebuilding of images__// 28 28 Changing the list of flows that should run on a container will now trigger the rebuilding of images.