Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 180.1
edited by Carlijn Kokkeler
on 2023/10/12 14:08
Change comment: There is no comment for this version
To version 181.1
edited by Erik Bakker
on 2023/10/12 16:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -10,8 +10,10 @@
10 10  == **Deployment Plan** ==
11 11  
12 12  //__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is now stopped first, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
13 +The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
14 14  
15 +{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
16 +
15 15  //__Editing release properties__//
16 16  With this release, it will be possible to change the description of a property by editing the property.
17 17