allow running OpenQA in docker container, add logging instead of printing to stdout
ClosedPublic

Authored by garretraziel on Jul 8 2015, 2:20 PM.

Details

Summary

Code is little bit reformatted (it's more PEP8-ish), logging is introduced instead
of output to stdout and several new options are added - user can specify directory
for downloading isos and he can also specify docker container where openqa is
running. Info about newest tested version is not written if no images were found.

Test Plan

Run trigger with several options. Tried F22 Final RC1 in docker.

Diff Detail

Repository
rOPENQA fedora_openqa
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
garretraziel retitled this revision from to allow running OpenQA in docker container, add logging instead of printing to stdout.Jul 8 2015, 2:20 PM
garretraziel updated this object.
garretraziel edited the test plan for this revision. (Show Details)
garretraziel added reviewers: jskladan, adamwill.
garretraziel added inline comments.Jul 9 2015, 6:10 AM
tools/openqa_trigger/openqa_trigger.py
369

I have moved -t argument from subparsers to main parser. This arguments are generic for all subparsers and I don't think that adding them to each one of them separately is a good idea.

Only inconvenience with this solution is that user has to specify "generic" arguments before specific arguments for subparsers, e. g. user has to write python openqa_trigger.py -t -d openqa_webui -l info current and he can't use it like python openqa_trigger.py current -t -d openqa_webui -l info.

This revision is now accepted and ready to land.Jul 9 2015, 8:19 AM
This revision was automatically updated to reflect the committed changes.