QA » openQA Project

I have it working in the sense that with https://github.com/Martchus/os-autoinst-distri-example/pull/1 I am able to:

• trigger jobs by scheduling a product.
• waiting until all jobs are done/cancelled and returning an exit code depending on the results.
• pass all settings as wanted, e.g. CASEDIR from Git and a relative NEEDLES_DIR within the same Git repo.
• references to CASEDIR and NEEDLES_DIR are generally handled correctly by the openQA worker (with NEEDLES_DIR=%25%25CASEDIR%25%25/needles syntax).

An example output looks like this:

Parameters for job creation: -d CASEDIR=https://github.com/Martchus/os-autoinst-distri-example.git#1/merge -d NEEDLES_DIR=%25%25CASEDIR%25%25/needles -d BUILD=Martchus/os-autoinst-distri-example.git#1/merge -d DISTRI=example -d GROUP_ID=0 -d VERSION=0 -d FLAVOR=DVD -d ARCH=x86_64 -d TEST=simple_boot --data-urlencode SCENARIO_DEFINITIONS_YAML@scenaio-definitions.yaml ***/api/v1/isos
Posted job with IDs: 3535
Job state of job ID 3535: running, waiting…
Job ID 3535 is 'done' with result 'incomplete'
Error: Process completed with exit code 10.

This test incompleted due to https://bugzilla.opensuse.org/show_bug.cgi?id=1208248. However, even without this bug it likely would have ended up incomplete as I still have to sort out a few things. What's missing is basically:

• that os-autoinst actually checks out the specified CASEDIR correctly as it so far doesn't checks out the PR branch. I'll either have to change how the CASEDIR is specified or how os-autoinst does the checkout.
• that there's actually a meaningful test scenario present. However, so far it isn't clear to me where e.g. the "ISO" is supposed to come from and whether that's within the scope of this ticket.

This PR would fix the first missing point: https://github.com/os-autoinst/os-autoinst/pull/2263 - see its commit message for details

The PR https://github.com/os-autoinst/os-autoinst/pull/2263 has been merged. That leaves the following open points:

• Move script for triggering (https://github.com/Martchus/os-autoinst-distri-example/pull/1) into a separate, re-usable repo or change the openQA-API so the script could be a one-liner. I don't think the latter is not possible because the script will always have to poll and evaluate JSON and deal and do proper error handling. That's in my opinion just too much for something we'd encourage people to C&P. So I'd file a ticket for moving the script into a separate repo, making it a reusable GitHub action.
  • Another time-boxed task to build the monitoring-shell script from https://github.com/Martchus/os-autoinst-distri-example/pull/1 into openqa-cli (with Perl code).
    • Created #125720 for that.
    • The client could also validate the YAML locally. The schema is already packaged with it. I added a remark about it on #92311#note-9.
  • Provide a ready-to-use container with all dependencies to create and monitor openQA jobs from GitHub actions.
    • Created #125723 for that.
    • Alternative: Create a GitHub-action repo
• Conduct a walk though of https://github.com/os-autoinst/openQA/pull/4999 with @okurz and others. There are already small remarks to be fixed (that I could still fix within the 20 hours). If the whole code needs to be rewritten due to some crazy ideas we need a new ticket for that, though.
  • The outcome of the walk tough is to handle remaining points as stated in #92311#note-8.