Changes for page 215 - Tiny Tales
Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
on 2023/12/21 16:18
Change comment:
There is no comment for this version
To version 158.1
edited by Carlijn Kokkeler
on 2023/11/21 12:42
on 2023/11/21 12:42
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 11-Log Luminary1 +209 - Max Verstappen - Content
-
... ... @@ -1,31 +1,31 @@ 1 -In the last sprint cycle, we focused on improving severalaspects related overviewsandlogging.Itisnow possibleosee anoverview ofall runtimesonrunning machines, seeruntimesandow versions inthemissingpropertiesoverview,andseewhich runtimeswill berestarted orredeployedina pop-updisplayedwhenstartingthe deploymentplan.Moreover,crashhandlinghasbeen improved,as well as runtimeoggingand the displayof thedeploymentexecutionerror message.Lastly, severalother minor changes andugfixeshave beenone,mainlyrelating totheDeploy and Managephase.1 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.2 11-Log Luminary||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]]. 4 4 5 5 =====New features===== 6 6 7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 7 +* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. 8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 9 +* All - The next generation architecture is the default now. New models will use this generation as default. 9 9 10 10 11 11 12 - 13 - 14 14 =====Minor changes===== 15 15 16 -* Deploy - Deployment:Themissingproperties overviewhasbeenupdatedtoshowtheruntimesandflowversionsof missingpropertyvalues.17 -* Deploy - Architecture:Pendingchangesthathaveahighrisk levelre nowshownin redboldin thepopup that appearsafterclicking'Applytoenvironment'.18 -* Manage - Monitoring: Weimprovedcrashhandlingso thatlog messagesclearlyshow when and why acontainerfailedtostart.15 +* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. 16 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well. 17 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps. 19 19 20 20 21 21 21 +====Bug fixes==== 22 22 23 +====Infra and image changes==== 23 23 24 - ====Bug fixes====25 +* Infra: New logging feature enabling us to make better choices in encryption standards. 25 25 26 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. 27 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container. 28 28 29 29 30 30 31 31 31 +