osmo-gsm-tester should tell jenkins where to find test result files
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.
#6 Updated by neels over 2 years ago
- Status changed from New to Resolved
In the new setup on the public jenkins, where a build slave actually runs on the main unit, this is solved by keeping the trial entirely within the jenkins workspace.
If we're going to implement a daemon to schedule test runs concurrently, this is still an open question, which we will come back to once we need to.