Use Case: Deploying Software Through the Test and Release Process Using Test Clients

100

If you do not want to install new software or a new software version directly on all Clients, but instead want to test it on a few selected Clients before releasing it, you can do so using the test and release process in Managed Software.

8

Proceed as follows:

9

10

= 1. Subscribe to the software =

11

12

Subscribe to the desired software - in this case, Mozilla Firefox 64-bit - in the Managed Software plugin, either via the Managed Software First Steps wizard or by clicking the Subscribe button on the ribbon bar.

13

14

The software package now appears on the Managed Software default Dashboard.

15

16

= **2. Define a custom test and release process** =

17

18

After you subscribe to a package, the package download begins and the software automatically enters the release process. This is indicated in the default Dashboard by the “R” (R = Release) following the version number. In this case, the standardized default process applies, in which software packages are released to Clients without going through the test rings

19

20

21

The default process has been configured so that the administrator normally no longer needs to intervene in this automated process, and the software automatically enters the Release Ring. The test and Release Rings are optional and therefore differ from the default process, so the process must be customized here.

[[image:ACMP.68.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@68_Managed Software_Default-Prozess des Softwarepakets_763.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]

26

27

28

The default process applies to the software package

To customize this later, select the software (or the new version) and click //Change Distribution Ring// on the ribbon bar. In the Distribution Ring Editor, specify //Distribution Ring 1// and leave the checkbox //Automatically move items to the next distribution ring// enabled so that this automatic process takes effect and the software is moved to the next two rings at a later time.

33

34

You then have the option to either change the default test and release process entirely or create a new one for the software packages. Go to //System > Settings > Managed Software > Testing and Release// to access all existing test and release processes.

35

36

* **Change the Entire Default Process**:

37

Click the Edit button and then, in the window that appears, click the //Test and Release Ring configuration// tab. Here you can edit the default settings. In this case, the “No Ring” setting is bypassed by enabling the corresponding checkbox, so that the subscribed software is moved directly to Test Ring 1. Then specify the number of days after which the software package is moved to the next test ring or to the Release Ring—in this example, after 2 and 3 days.

38

* **Create a new test and release process**:

39

Instead of clicking the Edit button, click //Add//. In the window that appears, enter a new name for the process and, if desired, a description. In the next step, use the corresponding button to add Mozilla Firefox 64-bit. You will then be returned to the settings overview for the test and release processes. Define this process as described above.

40

41

42

[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@1_Einstellungen im Test- und Freigabeprozess ändern.PNG||data-cmp-info="10" height="578" width="859"]]

43

44

Settings in the Default Process

45

46

47

Using this created or customized test and release process, the software package does not go directly to the Release Ring, but rather to Test Ring 1. This gives you the opportunity to test the desired software in advance.

48

49

= **3. Create a Container** =

50

51

In the next step, you must create a container for each test ring. This allows you to automatically deploy the software packages to the desired Clients in each test ring.

52

53

In the navigation pane, click //Add// under //Containers// on the ribbon bar. Enter //Test Ring 1// as the container name, and under //Run Windows Update Management and Managed Software Jobs in this distribution ring//, select the //Test Ring 1// option.

54

55

56

[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@Container.PNG||data-cmp-info="10" height="539" width="852"]]

57

58

59

Set container properties

If you want your test clients to be dynamically linked via a filter, you can apply it in the next step of the wizard. If this does not apply to your 5 selected clients, you do not need to apply a filter in the wizard and can add them statically afterward using a Query. Then click Done.

64

65

The newly created container appears in the container list. To ensure that the clients are dynamically linked to the containers based on the filter, you must trigger the linking process by clicking the //Calculate Shortcuts// button. Only then will the desired clients be placed in the newly created container.

66

67

To statically add the 5 clients, select the //Test Ring 1// container and click //Add// on the ribbon bar. An overview of the available Queries will appear. Find the appropriate Query for your clients to choose your test clients. They will then appear in the //Clients// tab.

68

69

70

[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@64_Managed Software_Use Case_1715.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]

71

72

73

Clients in Container Test Ring 1

= **4. Add a job to the container** =

78

79

To ensure that the container you created also performs the installation of the desired software on the 5 test clients, you must add a job to the container.

80

81

To do this, select the //Test Ring 1// container and go to the //Jobs > Add// tab. In the window that appears, select //Managed Software// as the //Job Type//.

82

83

84

[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@Container Job 1.PNG||data-cmp-info="10" height="623" width="825"]]

Select Job Type

Then double-click to select the software - in this case, //Mozilla Firefox 64-bit//. Next, click the Mozilla Firefox entry on the right to configure the settings. Here, for example, you can specify what should happen with the software on the Clients. In this case, it should be installed on the 5 test Clients, or updated if it is already present on the Client.

92

93

94

[[image:ACMP.68.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@Container Job.PNG||data-cmp-info="10" height="610" width="816"]]

95

96

97

Parameter settings for the job

Next, specify the start conditions - when the container job you created should execute. If you do not specify this, the job will execute every hour by default.

102

103

104

Please note that the Job Scanner must have run on the Client in order to execute the job.

105

106

107

The container job you created will now install the //Mozilla Firefox 64-bit// software on the 5 test clients in the //Test Ring 1// container at the times you specified.

108

109

110

= **5. Create the //Test Ring 2// and the //Release Ring// containers** =

111

112

Repeat this process starting with Step 3 once for Test Ring 2 and once for the Release Ring. In Test Ring 2, you can then optionally add, for example, 10 clients from different departments to the newly created //Test Ring 2// container. You can then add clients to the //Release Ring// container - either dynamically or statically via the dynamic Client link - who will ultimately receive Mozilla Firefox.

113

114

115

Please note that when creating the container, you must select the correct distribution ring under //Windows Update Management and Execute Managed Software Jobs in this Distribution Ring//! For the //Test Ring 2// container, select the //Test Ring 2// option, and for the //Release Ring// container, select //Released//.

116

Wiki source code of Use Case: Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen

Navigation

author	version	line-number	content
		1	{{aagon.priorisierung}}
		2	100
		3	{{/aagon.priorisierung}}
		4
		5	{{aagon.floatingbox/}}
		6
		7	If you do not want to install new software or a new software version directly on all Clients, but instead want to test it on a few selected Clients before releasing it, you can do so using the test and release process in Managed Software.
		8	Proceed as follows:
		9
		10	= 1. Subscribe to the software =
		11
		12	Subscribe to the desired software - in this case, Mozilla Firefox 64-bit - in the Managed Software plugin, either via the Managed Software First Steps wizard or by clicking the Subscribe button on the ribbon bar.
		13
		14	The software package now appears on the Managed Software default Dashboard.
		15
		16	= 2. Define a custom test and release process =
		17
		18	After you subscribe to a package, the package download begins and the software automatically enters the release process. This is indicated in the default Dashboard by the “R” (R = Release) following the version number. In this case, the standardized default process applies, in which software packages are released to Clients without going through the test rings
		19
		20	{{aagon.infobox}}
		21	The default process has been configured so that the administrator normally no longer needs to intervene in this automated process, and the software automatically enters the Release Ring. The test and Release Rings are optional and therefore differ from the default process, so the process must be customized here.
		22	{{/aagon.infobox}}
		23
		24	{{figure}}
		25	[[image:ACMP.68.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@68_Managed Software_Default-Prozess des Softwarepakets_763.png\|\|data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
		26
		27	{{figureCaption}}
		28	The default process applies to the software package
		29	{{/figureCaption}}
		30	{{/figure}}
		31
		32	To customize this later, select the software (or the new version) and click //Change Distribution Ring// on the ribbon bar. In the Distribution Ring Editor, specify //Distribution Ring 1// and leave the checkbox //Automatically move items to the next distribution ring// enabled so that this automatic process takes effect and the software is moved to the next two rings at a later time.
		33
		34	You then have the option to either change the default test and release process entirely or create a new one for the software packages. Go to //System > Settings > Managed Software > Testing and Release// to access all existing test and release processes.
		35
		36	* Change the Entire Default Process:
		37	Click the Edit button and then, in the window that appears, click the //Test and Release Ring configuration// tab. Here you can edit the default settings. In this case, the “No Ring” setting is bypassed by enabling the corresponding checkbox, so that the subscribed software is moved directly to Test Ring 1. Then specify the number of days after which the software package is moved to the next test ring or to the Release Ring—in this example, after 2 and 3 days.
		38	* Create a new test and release process:
		39	Instead of clicking the Edit button, click //Add//. In the window that appears, enter a new name for the process and, if desired, a description. In the next step, use the corresponding button to add Mozilla Firefox 64-bit. You will then be returned to the settings overview for the test and release processes. Define this process as described above.
		40
		41	{{figure}}
		42	[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@1_Einstellungen im Test- und Freigabeprozess ändern.PNG\|\|data-cmp-info="10" height="578" width="859"]]
		43
		44	Settings in the Default Process
		45	{{/figure}}
		46
		47	Using this created or customized test and release process, the software package does not go directly to the Release Ring, but rather to Test Ring 1. This gives you the opportunity to test the desired software in advance.
		48
		49	= 3. Create a Container =
		50
		51	In the next step, you must create a container for each test ring. This allows you to automatically deploy the software packages to the desired Clients in each test ring.
		52
		53	In the navigation pane, click //Add// under //Containers// on the ribbon bar. Enter //Test Ring 1// as the container name, and under //Run Windows Update Management and Managed Software Jobs in this distribution ring//, select the //Test Ring 1// option.
		54
		55	{{figure}}
		56	[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@Container.PNG\|\|data-cmp-info="10" height="539" width="852"]]
		57
		58	{{figureCaption}}
		59	Set container properties
		60	{{/figureCaption}}
		61	{{/figure}}
		62
		63	If you want your test clients to be dynamically linked via a filter, you can apply it in the next step of the wizard. If this does not apply to your 5 selected clients, you do not need to apply a filter in the wizard and can add them statically afterward using a Query. Then click Done.
		64
		65	The newly created container appears in the container list. To ensure that the clients are dynamically linked to the containers based on the filter, you must trigger the linking process by clicking the //Calculate Shortcuts// button. Only then will the desired clients be placed in the newly created container.
		66
		67	To statically add the 5 clients, select the //Test Ring 1// container and click //Add// on the ribbon bar. An overview of the available Queries will appear. Find the appropriate Query for your clients to choose your test clients. They will then appear in the //Clients// tab.
		68
		69	{{figure}}
		70	[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@64_Managed Software_Use Case_1715.png\|\|data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
		71
		72	{{figureCaption}}
		73	Clients in Container Test Ring 1
		74	{{/figureCaption}}
		75	{{/figure}}
		76
		77	= 4. Add a job to the container =
		78
		79	To ensure that the container you created also performs the installation of the desired software on the 5 test clients, you must add a job to the container.
		80
		81	To do this, select the //Test Ring 1// container and go to the //Jobs > Add// tab. In the window that appears, select //Managed Software// as the //Job Type//.
		82
		83	{{figure}}
		84	[[image:ACMP.63.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@Container Job 1.PNG\|\|data-cmp-info="10" height="623" width="825"]]
		85
		86	{{figureCaption}}
		87	Select Job Type
		88	{{/figureCaption}}
		89	{{/figure}}
		90
		91	Then double-click to select the software - in this case, //Mozilla Firefox 64-bit//. Next, click the Mozilla Firefox entry on the right to configure the settings. Here, for example, you can specify what should happen with the software on the Clients. In this case, it should be installed on the 5 test Clients, or updated if it is already present on the Client.
		92
		93	{{figure}}
		94	[[image:ACMP.68.Use Cases.Managed Software.Software mithilfe von Test-Clients über den Test- und Freigabeprozess verteilen.WebHome@Container Job.PNG\|\|data-cmp-info="10" height="610" width="816"]]
		95
		96	{{figureCaption}}
		97	Parameter settings for the job
		98	{{/figureCaption}}
		99	{{/figure}}
		100
		101	Next, specify the start conditions - when the container job you created should execute. If you do not specify this, the job will execute every hour by default.
		102
		103	{{aagon.infobox}}
		104	Please note that the Job Scanner must have run on the Client in order to execute the job.
		105	{{/aagon.infobox}}
		106
		107	The container job you created will now install the //Mozilla Firefox 64-bit// software on the 5 test clients in the //Test Ring 1// container at the times you specified.
		108
		109
		110	= 5. Create the //Test Ring 2// and the //Release Ring// containers =
		111
		112	Repeat this process starting with Step 3 once for Test Ring 2 and once for the Release Ring. In Test Ring 2, you can then optionally add, for example, 10 clients from different departments to the newly created //Test Ring 2// container. You can then add clients to the //Release Ring// container - either dynamically or statically via the dynamic Client link - who will ultimately receive Mozilla Firefox.
		113
		114	{{aagon.infobox}}
		115	Please note that when creating the container, you must select the correct distribution ring under //Windows Update Management and Execute Managed Software Jobs in this Distribution Ring//! For the //Test Ring 2// container, select the //Test Ring 2// option, and for the //Release Ring// container, select //Released//.
		116	{{/aagon.infobox}}