Wiki source code of Deploy a release

Last modified by Erik Bakker on 2024/03/07 11:42
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3
4 In this microlearning, we will focus on the situation where a change in your environment needs to be deployed to an environment. A change can be a flow update, a property addition or update, or an update in the "base image" of eMagiz.
5
6 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7
8 == 1. Prerequisites ==
9
10 * Basic knowledge of the eMagiz platform
11 * Understanding of Releases and how to set up a Deployment plan
12 * Edit rights for your environment in Deploy
13 * A change that is added to a release so you can try it yourself
14
15 == 2. Key concepts ==
16
17 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 that all changes made to the release compared to the running environment before executing the deployment plan are applied effectively.
18
19 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-execute-deployment-plan-gen3--execute-release-button.png]]
20
21 == 3. Execute a Deployment plan ==
22
23 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 showing the deployment steps' progress. Pressing the green **play** button will start the execution of the deployment plan.
24
25 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-execute-deployment-plan-gen3--overview-default-steps.png]]
26
27 Should eMagiz not be able to execute a specific 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.
28
29 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-execute-deployment-plan-gen3--feedback-to-user.png]]
30
31 {{info}}Key notes to consider during the execution of the deployment plan
32
33 * All containers (i.e. runtimes) for which **a change** is scheduled will be updated. The following criteria are used to determine whether a change is necessary:
34 ** Update in at least **one** flow version compared to the active "deployed version."
35 ** Addition or update of properties created via a **functional** release or a **property** release. Please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] for information on release properties.
36 ** New "base image" issued by eMagiz. Please keep an eye on the [[release notes>>Main.Release Information.Portal.WebHome||target="blank"]] to see when this happens. Search for "eMagiz version" in Manage to see which image you are currently running.
37 * The middle section showing the integration landscape is highlighting in what system the deployment of a flow is happening
38 * The right-hand panel shows the log messages from the runtimes where the deployment(s) of runtime are taking place. Look out for "Started eMagiz" logging
39 * A message will be displayed that the deployment is completed{{/info}}
40
41 == 4. Key takeaways ==
42
43 * The execution of a deployment plan is a smooth process to avoid manual deployments of flows
44 * Be aware of the specific considerations involved
45 * Tune the deployment plan continuously to make it better all the time.
46
47 == 5. Suggested Additional Readings ==
48
49 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.
50 )))((({{toc/}}))){{/container}}
51 {{/container}}