Project

General

Profile

Actions

Feature #2205

closed

osmo-gsm-tester should tell jenkins where to find test result files

Added by neels about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
-
Target version:
-
Start date:
04/27/2017
Due date:
% Done:

0%

Spec Reference:

Description

To find the results xml file and possibly to archive test results, jenkins should be told which run directory is being set up by the test run it invokes. For a manual test run of osmo-gsm-tester.py, it makes sense to output the log on stdout/stderr. For a jenkins invocation, that doesn't make all that much sense.

Add a command line option '-q' / '--quiet' to osmo-gsm-tester.py that causes it to be quiet on stdout, except for printing each run dir that is created to run tests.
In contrib/jenkins.sh, invoke osmo-gsm-tester.py -q and collect stdout in a shell variable. This can then be used to retrieve results like the log or junit xml files.


Related issues

Related to OsmoGSMTester - Feature #2206: osmo-gsm-tester should write to a log file, not only stdoutClosedneels04/27/2017

Actions
Blocks OsmoGSMTester - Feature #2201: osmo-gsm-tester: compose jenkins result XMLClosedpespin04/26/2017

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)