Skip to Content

Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08
From version 294.1
edited by Carlijn Kokkeler
on 2024/04/18 13:08
Change comment: There is no comment for this version
To version 288.1
edited by Carlijn Kokkeler
on 2023/12/06 08:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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.
... ... @@ -57,7 +57,7 @@
57 57  * [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
58 58  
59 59  
60 -== **Key Takeaways** ==
57 +== **Key takeaways** ==
61 61  
62 62  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:
63 63  
... ... @@ -65,7 +65,7 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.210 - Deployment Delights.WebHome||target="blank"]]
65 +* Check out the release notes [here]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 71  * Upgrade to the latest build number