Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ts_main_telescope
-
Labels:
-
Story Points:3
-
Epic Link:
-
Sprint:TSSW Sprint - Aug 17 - Aug 31
-
Team:Telescope and Site
-
Urgent?:No
Description
Test the Jenkins with LabVIEW on my desktop to see it can do the unit test, generate the Junit xml reports, and publish or not. I think it might be easier to use the virtual box to do this test (install the Jenkins in the virtual box).
Attachments
Issue Links
- is triggering
-
DM-26743 Test the CTIO Jenkins and Docker Image from Nexus
- Done
Instead of LabVIEWCLI, I executed the "timeout + labview64" to finish the unit test and publish the result as the following:

However, the test is identified as failed. Need to check where is the problem. Added the "command || true" to circumvent this. This implies the developer can only based on the report to know the unit test results. The stage will always show true.