Changes for page Setting up a deployment plan
Last modified by Erik Bakker on 2024/02/20 08:30
From version 29.1
edited by Erik Bakker
on 2022/10/18 08:42
on 2022/10/18 08:42
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.eMagiz - Default language
-
... ... @@ -1,1 +1,0 @@ 1 -en - Content
-
... ... @@ -1,23 +1,28 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 2 3 -In this microlearning, we will focus on settingupa deploymentplanandlearn aboutthe considerationswhensettingup suchadeploymentplan.3 +In this microlearning, we will focus on the various options to create and edit properties i.e. property management. 4 4 5 5 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 6 6 7 +* Last update: February 4th, 2021 8 +* Required reading time: 4 minutes 9 + 7 7 == 1. Prerequisites == 8 8 9 9 * Basic knowledge of the eMagiz platform 10 10 * Understand eMagiz releases in basics 11 -* Have an environment where you can add releases that is operational to try out the deployment plan 14 +* Have an environment where you can add releases and that is operational to try out the deployment plan 12 12 13 13 == 2. Key concepts == 14 14 15 -This microlearning centers around the Deployment plan. The deployment plan is a series of steps that must be executed on a TAP environment todeploythe(active)release. Active in that all changes made to the release compared to the running environmentare applied effectivelybefore executing the deployment.18 +This microlearning centers around the Deployment plan. The deployment plan is a series of steps that need to be executed on a TAP environment to make the release defined as active. Active in the sense that all changes made to the release compared to the running environment before executing the deployment plan are applied effectively. 16 16 17 -The Deployment plan is defined in the Deployment Plan section under Deploy. Each Test, Acceptance ,and Production environment hasitsplan, andthe plan may vary acrosstheenvironments. The Deployment plan is executed from therelease itself, using a Release'soptions.20 +The Deployment plan is defined in the Deployment Plan section under Deploy. Each Test, Acceptance and Production environment have their plan, and across an environment, the plan may vary. The Deployment plan is executed from the Release itself, using the options that a Release has. 18 18 19 19 [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] 20 20 24 + 25 + 21 21 == 3. Defining the Deployment plan == 22 22 23 23 Below is a screenshot of a very basic Deployment plan. In the next section, we'll take a look at the options available for configuration. These are referred to as steps and can be added with the button New as can be seen below. ... ... @@ -54,6 +54,8 @@ 54 54 * Copy the plan to the next environment to align all plans in the same way. 55 55 * Ensure to have a Prepare deployment step in your work definition (sprint) and improve the deployment at each iteration 56 56 62 + 63 + 57 57 == 4. Assignment == 58 58 59 59 Go to your environment, and try to add a deployment plan for your environment. Experiments with all options, and ensure to run the deployment plan at least once. Be so familiar with the plan that you will use this approach to refresh your environment at all times. ... ... @@ -65,6 +65,8 @@ 65 65 * The deployment plan is a must-have to deploy all the changes in an active release on an environment 66 66 * Keep the plan up to date is easy, and takes away the manual effort to deploy flows on the different runtimes. 67 67 75 + 76 + 68 68 == 6. Suggested Additional Readings == 69 69 70 70 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.