Changes for page 210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08

From version 258.1
edited by Carlijn Kokkeler
on 2023/11/21 12:35
Change comment: There is no comment for this version
To version 261.1
edited by Carlijn Kokkeler
on 2023/11/22 14:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,9 +9,9 @@
9 9  Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10 10  {{/warning}}
11 11  
12 -== **Quicker Deployment Plan** ==
12 +== **Quicker Deployment Plan Execution** ==
13 13  
14 -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. Moreover, we fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deployment plan will be finished much quicker now!
14 +We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
15 15  
16 16  == **Next Generation Architecture Default** ==
17 17  
... ... @@ -39,9 +39,6 @@
39 39  //__Queue explorer milliseconds__//
40 40  The queue browser now displays milliseconds in the timestamps.
41 41  
42 -//__Cancel and next buttons order__//
43 -The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
44 -
45 45  //__Unused images__//
46 46  When a release is removed, the related unused images in the on-premises machines will be removed as well.
47 47