Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 336.1
edited by Carlijn Kokkeler
on 2024/01/15 14:15
Change comment: There is no comment for this version
To version 276.1
edited by Carlijn Kokkeler
on 2023/12/04 14:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +209 - Deployment Delights
Content
... ... @@ -3,23 +3,44 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
6 +**Hi there, eMagiz developers!** We have...
7 7  
8 +== **Release Maintenance** ==
9 +
10 +
11 +
12 +
13 +
8 8  == **Feedback Items** ==
9 9  
10 -//__Failover setup__//
11 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]].
16 +//__Harbor port change__//
17 +The port for which you need to register has been changed ...?
12 12  
19 +//__Container version overview__//
20 +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.
13 13  
22 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
23 +
24 +//__Unchanged containers__//
25 +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 +
27 +//__Rebuilding of images__//
28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 +
30 +
14 14  == **Bug Fixes** ==
15 15  
33 +//__Runtime metrics processing__//
34 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
16 16  
36 +//__Deployment plan__//
37 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
17 17  
18 18  == **Fancy Forum Answers** ==
19 19  
20 20  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
21 21  
22 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
43 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
23 23  
24 24  == **Key takeaways** ==
25 25  
... ... @@ -32,6 +32,7 @@
32 32  * Check out the release notes [here]
33 33  * Start thinking about how the license tracker can aid your development
34 34  * Start thinking about major, minor, and patch
56 +* Upgrade to the latest build number
35 35  * Keep making great integrations
36 36  
37 37  Let's stay in touch and till next time!
... ... @@ -39,6 +39,7 @@
39 39  {{info}}
40 40  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
41 41  
64 +~*~* Indicates a next-generation-architecture only feature.
42 42  {{/info}}
43 43  )))
44 44