action #162515
Updated by okurz 28 days ago
### Motivation
As findings in #161879#note-6 reveal, the change to make scheduling more dynamically needs to be done in `openqa-trigger-from-obs` directly (as the openQA sync plugin is just a script runner and frontend). There are various ways to influence the job scheduling, e.g. adding support for invoking a hook script which could again be done on various levels/places. One could alter the script generator (`scriptgen.py`) directly to change the generated scripts or one could alter `rsync.sh` as shown in https://github.com/os-autoinst/openqa-trigger-from-obs/pull/249. It is also questionable whether we still want to top-level script generator (`scriptgen.py`). The point is: **There are many options to discuss/explore.** If we just make it print "Hello world" *somehow*/*somewhere* as a first step this is *not* going to help us find what we need to solve the actual problem.
### Acceptance criteria
* **AC1**: We know what we need to change in our current mechanism for triggering tests in the light of #159828.
* **AC2**: We know who (which team) is going to change what parts.
### Suggestion
* Read #161879#note-6 and related source files to get an idea of how openqa-trigger-from-obs works
* Conduct a pair programming session with members from QE Core and QE Tools (or possibly other interested teams) to come up with a draft PR for https://github.com/os-autoinst/openqa-trigger-from-obs.
Back