Skip to Content
Last modified by Erik Bakker on 2024/06/24 14:46
From version 9.1
edited by Erik Bakker
on 2022/10/28 14:14
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/10/28 14:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -28,7 +28,7 @@
28 28  * After installing any build 50 (or higher) flow, build 48 (or lower) flows containing a Jetty server on the same runtime cannot be started anymore. If it is really necessary to still install/start a build 48 (or lower) Jetty server flow: uninstall all build 50 (or higher) flows on that runtime first, then install/start the build 48 (or lower) Jetty server flow, and finally re-install the build 50 (or higher) flows.
29 29  * When deploying a flow containing a Jetty server, the infra flow of that runtime must have a matching build number, that is: if the the Jetty server flow is build 48 (or lower) the infra needs to be build 48 (or lower) as well, if the Jetty server flow is build 50 (or higher) the infra needs to be 50 (or higher) as well.
30 30  
31 --> Impact: review the runtimes that have flows with a Jetty component and ensure that matching buildnumbers are inside these runtimes for all flows.
31 +**Impact**: review the runtimes that have flows with a Jetty component and ensure that matching buildnumbers are inside these runtimes for all flows.
32 32  
33 33  === 3.2 Upgrade ===
34 34  
... ... @@ -36,7 +36,7 @@
36 36  
37 37  === 3.3 Functional changes ===
38 38  
39 -Before an environment is updates to the flows with the latest releases, it is advices to first check which flows have functional changes. These flows need to be tested and put into production first so that you can isolate issues in case they occur. Once these flows are tested and live, only then move the flows witht the new buildnumbers from test to production.
39 +Before an environment is updates to the flows with the latest releases, it is adviced to first check which flows have functional changes. These flows need to be tested and put into production first so that you can isolate issues in case they occur. Once these flows are tested and live, only then move the flows with the new buildnumbers from test to production.
40 40  
41 41  === 3.4 Approach ===
42 42