Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 290.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version
To version 287.1
edited by Carlijn Kokkeler
on 2023/12/04 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,12 +3,12 @@
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!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 8  == **Alerts** ==
9 9  
10 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.
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
12 12  
13 13  //__Missing metrics alert__//
14 14  We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
... ... @@ -15,16 +15,13 @@
15 15  
16 16  == **Feedback Items** ==
17 17  
18 -//__Improved release build process__//
19 -When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
20 -
21 21  //__Container version overview__//
22 -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.
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.
23 23  
24 24  [[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
25 25  
26 -//_Improved deployment process_//
27 -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.
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.
28 28  
29 29  //__Rebuilding of images__//
30 30  Changing the list of flows that should run on a container will now trigger the rebuilding of images.
... ... @@ -35,7 +35,7 @@
35 35  The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
36 36  
37 37  //__Deployment plan__//
38 -We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
39 39  
40 40  //__View all store items__//
41 41  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.
... ... @@ -44,7 +44,7 @@
44 44  We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
45 45  
46 46  //__Max fetch size__//
47 -In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
44 +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.
48 48  
49 49  == **Fancy Forum Answers** ==
50 50