Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 289.1
edited by Carlijn Kokkeler
on 2023/12/06 13:20
Change comment: There is no comment for this version
To version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +211 - Log Luminary
Content
... ... @@ -3,25 +3,26 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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.
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Alerts** ==
8 +== **TBD** ==
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.
12 12  
13 -//__Missing metrics alert__//
14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 15  
16 16  == **Feedback Items** ==
17 17  
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 +
18 18  //__Container version overview__//
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. By having this overview, you can check which versions of the containers that exist in Deploy Architecture are in the release.
20 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
20 20  
21 21  [[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
22 22  
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. This decreases the deployment time and improves the performance.
24 +//__Improved deployment process__//
25 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
25 25  
26 26  //__Rebuilding of images__//
27 27  Changing the list of flows that should run on a container will now trigger the rebuilding of images.