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
@@ -31,6 +31,7 @@ Replaces xml_files/enb_usrp210_band40_test_05mhz_tm1.xml
|
||||
100000
|
||||
111110
|
||||
040101
|
||||
800813
|
||||
030104
|
||||
040301 040501 040602 040601 040603 040604 040605 040642 040641 040643 040644 040645 040401 040201
|
||||
030204
|
||||
@@ -64,7 +65,12 @@ Replaces xml_files/enb_usrp210_band40_test_05mhz_tm1.xml
|
||||
<node>starsky</node>
|
||||
<command>sudo -S b2xx_fx3_utils --reset-device</command>
|
||||
</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="030104">
|
||||
<class>Deploy_Object</class>
|
||||
<desc>Deploy eNB (TDD/Band40/5MHz/B200) in a container</desc>
|
||||
|
||||
Reference in New Issue
Block a user