Changes for page 210 - Deployment Delights

Summary

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

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.