Changes for page 213 - Joyful Journeys

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Deployment Delights
	1	+203 - Fast Paced

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,51 +1,41 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have...
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
7	7
8		-== **Release Maintenance** ==
	7	+== **Release Properties - Early Feedback** ==
	8	+The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
9	9
10		-
11		-
12		-
13		-
14	14	== **Feedback Items** ==
15	15
16		-//__Container version overview__//
17		-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.
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
20	20
21		-//__Unchanged containers__//
22		-When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23		-
24		-//__Rebuilding of images__//
25		-Changing the list of flows that should run on a container will now trigger the rebuilding of images.
26		-
27		-
28	28	== **Bug Fixes** ==
29	29
30		-//__Runtime metrics processing__//
31		-The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	20	+//__Ensure no flow can be in a release twice__//
	21	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
32	32
33		-//__Deployment plan__//
34		-We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
35	35
36	36	== **Fancy Forum Answers** ==
37	37
38	38	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:
39	39
40		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	30	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
41	41
42	42	== **Key takeaways** ==
43	43
44		-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:
	34	+Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
45	45
46	46	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47	47	* If you have feedback or ideas for us, talk to the Platypus
48		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	38	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49	49	* Clear your browser cache (Ctrl + Shift + Del)
50	50	* Check out the release notes [here]
51	51	* Start thinking about how the license tracker can aid your development
...	...	@@ -59,11 +59,5 @@
59	59	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60	60
61	61	~*~* Indicates a next-generation-architecture only feature.
62		-{{/info}}
63		-)))
64		-
65		-(((
66		-{{toc/}}
67		-)))
	52	+{{/info}})))((({{toc/}}))){{/container}}
68	68	{{/container}}
69		-{{/container}}