coordination #95377
Updated by szarate almost 3 years ago
There are cases where a request to test something specific comes to our backlog, but it really doesn't belong, as a result other teams, products might be blocked due to lack of knowledge or manpower that would allow them to schedule and test their own products/services in openQA. The purpose of this epic is to coordinate the effort needed to allow those teams to unblock themselves by: Providing a mechanism in openQA backend or the test repository to take parameters for the job definition, which ideally would pass those parameters to a test (either by parametrization, or clear variable definition in the test code), that would allow somebody to: - Pass an url pointing to a binary/rpm/script that lives either in gitlab.suse.de or in a OBS instance (openQA has a allowed URL list, which should be considered too) - Provide a script that interacts with the binary/rpm/script provided (openQA being agnostic to what was passed) and outputs either a `junit file`, `tap`, `IPA` or `LTP` `tap` (So that parse_extra_log (See supported formats by OpenQA::Parser) (OpenQA::Parser) is able to properly process the results) - Upon script execution, script call log is uploaded, along with the log produced by the script Instructions that allow the user to create their own jobgroup if required, or add it to the corresponding jobgroup, instructions on how to set the mantainer, etc.