Wiki source code of Deploy a release

Last modified by Erik Bakker on 2024/02/20 08:31
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 {{error}}
4 Note that the functionality mentioned in this microlearning will become obsolete when migrating to the new generation runtime.
5 {{/error}}
6
7 In this microlearning, we will focus on the situation where an existing property needs a change of value and how to put this value into effect in your environment.
8
9 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
10
11 == 1. Prerequisites ==
12
13 * Basic knowledge of the eMagiz platform
14 * Understanding of Releases and how to set up a Deployment plan
15 * Edit rights for your environment in Deploy
16 * A change made in a flow version that is added to a release so you can try it yourself
17
18 == 2. Key concepts ==
19
20 This microlearning centers around the execution of a Deployment plan. The deployment plan is a series of steps that need to be executed on any TAP environment to make the release defined active inside the eMagiz runtimes. Active in the sense that all changes made to the release compared to the running environment before executing the deployment plan are applied effectively.
21
22 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-execute-deployment-plan-pic1.png]]
23
24 == 3. Execute a Deployment plan ==
25
26 Provided there is a deployment plan, the execution is initialized from the Releases section. The button highlighted in the figure above is the button to start the deployment plan. The page below is then displayed as an example of the page that shows the progress of the deployment steps. Pressing the green play button will start the execution of the deployment plan.
27
28 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-execute-deployment-plan-pic2.png]]
29
30 Should eMagiz not be able to execute a certain step because the runtime is not reachable a pop-up is shown to the user informing the user that an action needs to be taken.
31
32 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-execute-deployment-plan-pic3.png]]
33
34 {{info}}Some key notes to consider during the execution of the plan
35
36 * Only the changed, added, or deleted flow will be considered for deployment. No change means that the current flow remains untouched
37 * The runtime that requires updates has to be started / active before anything can be deployed. See the screenshot below to see what happens if the runtime is not running at the moment of execution
38 * The middle section showing the integration landscape is highlighting in what system the deployment of a flow is happening
39 * The right-hand panel shows the log messages from the runtimes where the deployment(s) of flows are taking place
40 * A message will be displayed that the deployment is completed
41 * The deployment plan will by default cleanup old versions of flow (unless specified otherwise in the settings of the deployment plan).{{/info}}
42
43 == 4. Key takeaways ==
44
45 * The execution of a deployment plan is a smooth process to avoid manual deployments of flows
46 * Be aware of the specific considerations involved
47 * Tune the deployment plan continuously to make it better all the time.
48
49 == 5. Suggested Additional Readings ==
50
51 If you are interested in this topic and want more information on it please read the help text provided by eMagiz when executing these actions.
52 )))((({{toc/}}))){{/container}}
53 {{/container}}