Seperated Create_Workspace as a seperate XML task
Create_Workspace is used used in XML files instead of directly being executed in DeployObject(). This can be problematic if we deploy multiple services on the same host, since a previous workspace will be deleted. Also, it removes futile git clones. There are other XML steps (CppCheckAnalysis, LicenceAndFormattingCheck, BuildImage, BuildProxy, BuildClusterImage) that implicitly called Create_Workspace. Those calls have been removed and care has been taken to insert the corresponding Create_Workspace steps in the XML.
This commit is contained in:
committed by
Raphael Defosseux
parent
150a00bd23
commit
44d0c88863
@@ -29,7 +29,9 @@
|
||||
111111
|
||||
000222
|
||||
001111
|
||||
800813
|
||||
002222
|
||||
800814
|
||||
002223
|
||||
000111
|
||||
100000
|
||||
@@ -54,7 +56,12 @@
|
||||
<desc>Initialize Quectel</desc>
|
||||
<id>sphex_quectel</id>
|
||||
</testCase>
|
||||
|
||||
<testCase id="800813">
|
||||
<class>Create_Workspace</class>
|
||||
<desc>Creating new Workspace for server 0</desc>
|
||||
<eNB_instance>0</eNB_instance>
|
||||
<eNB_serverId>0</eNB_serverId>
|
||||
</testCase>
|
||||
<testCase id="002222">
|
||||
<class>Deploy_Object</class>
|
||||
<desc>Deploy PNF/Nvidia CUBB in a container</desc>
|
||||
@@ -63,7 +70,12 @@
|
||||
<eNB_instance>0</eNB_instance>
|
||||
<eNB_serverId>0</eNB_serverId>
|
||||
</testCase>
|
||||
|
||||
<testCase id="800814">
|
||||
<class>Create_Workspace</class>
|
||||
<desc>Creating new Workspace for server 0</desc>
|
||||
<eNB_instance>0</eNB_instance>
|
||||
<eNB_serverId>0</eNB_serverId>
|
||||
</testCase>
|
||||
<testCase id="002223">
|
||||
<class>Deploy_Object</class>
|
||||
<desc>Deploy VNF in a container</desc>
|
||||
|
||||
Reference in New Issue
Block a user