Skip to Content
Last modified by Erik Bakker on 2024/06/24 14:46
From version 2.1
edited by Erik Bakker
on 2022/06/10 08:37
Change comment: Imported from XAR
To version 6.1
edited by Carlijn Kokkeler
on 2022/10/05 16:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +Impact of buildnumber upgrades
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,20 +1,8 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -
5 -<div class="doc">
6 -
7 -
8 -
9 -= Impact of builnumber upgrades =
10 -
1 +{{container}}{{container layoutStyle="columns"}}(((
11 11  In this microlearning, we will focus on the helping you to assess the impact of upgrading to new buildnumbers.
12 12  
13 13  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
14 14  
15 -* Last update: August 27th, 2021
16 -* Required reading time: 5 minutes
17 -
18 18  == 1. Prerequisites ==
19 19  
20 20  * Advanced knowledge of the eMagiz platform
... ... @@ -26,13 +26,11 @@
26 26  
27 27  eMagiz works hard to limit the number of buildnumbers. The general approach for buildnumber is that these are backwards compatible, so the impact of moving to the next buildnumber poses a minimal impact and risk.
28 28  
29 -
30 -
31 31  == 3. Assessing the impact of changing buildnumbers ==
32 32  
33 33  === 3.1 Release notes & impact assessment ===
34 34  
35 -These can be found in the eMagiz Portal under Community --> Release notes. Check for the left hand menu called Build Numbers. Once the release notes are properly read, assess the impact. This effectively means that the key notes around the model components can be used.
21 +These can be found in the eMagiz Portal under Community -> Release notes. Check for the left hand menu called Build Numbers. Once the release notes are properly read, assess the impact. This effectively means that the key notes around the model components can be used.
36 36  
37 37  You see often a list of libraries that are updated, and these are the only notes that means that the impact is slim to none. Then make sure to read the notes above around the model components touched. These will help to asses the impact. Some model components have additional capability, and some have a limited capability or a fix.
38 38  
... ... @@ -42,7 +42,7 @@
42 42  * 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.
43 43  * 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.
44 44  
45 ---> 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.
46 46  
47 47  === 3.2 Upgrade ===
48 48  
... ... @@ -56,8 +56,6 @@
56 56  
57 57  It is usually best to update the test and acceptance environment first and leave that running for a certain grace period. So that in case potential issues can be fixed still.
58 58  
59 -
60 -
61 61  == 4. Assignment ==
62 62  
63 63  Take a look at the release notes in the eMagiz Portal to ensure you know where to look.
... ... @@ -70,8 +70,6 @@
70 70  * Read the release notes for builnumbers carefully to assess the impact - in case the impact is minimal proceed with the upgrade
71 71  * Make the buildnumber upgrades planable so the release schedule takes these actions into account.
72 72  
73 -
74 -
75 75  == 6. Suggested Additional Readings ==
76 76  
77 77  If you are interested in this topic and want more information on it, please read the release notes provided by eMagiz