Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 276.1
edited by CarlijnKokkeler
on 2023/12/04 14:43
Change comment: There is no comment for this version
To version 540.1
edited by CarlijnKokkeler
on 2024/06/03 13:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Deployment Delights
1 +222 - Flee Frustration
Content
... ... @@ -3,46 +3,40 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Release Maintenance** ==
9 -
10 -
11 -
12 -
13 -
14 14  == **Feedback Items** ==
9 +//__Cron triggers__//
10 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
15 15  
16 -//__Harbor port change__//
17 -The port for which you need to register has been changed ...?
12 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
18 18  
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.
14 +//__Design changes__//
15 +If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
17 +[[image:Main.Images.Release Blog.WebHome@release-222-affect-design-architecture.png]]
23 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 -
31 31  == **Bug Fixes** ==
20 +//__Trigger activation__//
21 +Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
32 32  
33 -//__Runtime metrics processing__//
34 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
23 +//__Multiple users deploying__//
24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
35 35  
36 -//__Deployment plan__//
37 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
38 38  
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
30 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
35 +* [[OAuth 2.0, 403 Forbidden>>https://my.emagiz.com/p/question/172825635703837388||target="blank"]]
36 +* [[HTTP request without reply>>https://my.emagiz.com/p/question/172825635703837492||target="blank"]]
37 +* [[All-entry API gateway is not starting>>https://my.emagiz.com/p/question/172825635703837607||target="blank"]]
44 44  
45 -== **Key takeaways** ==
39 +== **Key Takeaways** ==
46 46  
47 47  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
48 48  
... ... @@ -50,10 +50,9 @@
50 50  * If you have feedback or ideas for us, talk to the Platypus
51 51  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52 52  * Clear your browser cache (Ctrl + Shift + Del)
53 -* Check out the release notes [here]
47 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
54 54  * Start thinking about how the license tracker can aid your development
55 55  * Start thinking about major, minor, and patch
56 -* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,7 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -~*~* Indicates a next-generation-architecture only feature.
65 65  {{/info}}
66 66  )))
67 67