Allow to clone and monitor a job when creating a PR

[Martchus]

This change allows to clone a job when creating a PR by mentioning it in the PR description via @openqa: Clone https://openqa.opensuse.org/….

This requires the split-out monitor-subcommand provided by openQA PR os-autoinst/openQA#5482.

I tested this locally, e.g.:

cat .github/workflows/openqa.yml | yq -r '.jobs.clone_mentioned_job.steps[0].run' | env GH_REPO=foo GH_REF=bar OPENQA_HOST=http://127.0.0.1:9526 OPENQA_API_KEY=… OPENQA_API_SECRET=… GH_PR_BODY="Merge my changes\n\n @openqa: Clone http://127.0.0.1:9526/tests/4240  \nfootnote" DRY_RUN_JOB_IDS='{"4240" : 4246, "4239" : 4245}' bash
Cloned 'http://127.0.0.1:9526/tests/4240' into:
http://127.0.0.1:9526/tests/4246
http://127.0.0.1:9526/tests/4245
script/openqa-cli monitor … 4246 4245
{"blocked_by_id":null,"id":4246,"result":"none","state":"scheduled"}
Job state of job ID 4246: scheduled, waiting …
^C

It also works without DRY_RUN_JOB_IDS; then it actually clones the job and parses the output of openqa-clone-job.

---

Related ticket: https://progress.opensuse.org/issues/130934

[b10n1k]

Looks good but i want to mention that as it is, it seems to be designed multiple jobs, but it prevents to run simultaneously in both o3 and osd. i guess this is intended.

Another question: o3 and osd should have different keys. How the script knows which to use here?

[Martchus]

it prevents to run simultaneously in both o3 and osd. i guess this is intended.

Yes, OSD is out of scope for now. I know that limits the usefulness in practice greatly but GitHub just cannot access OSD.

[Martchus]

I updated this now to use os-autoinst/scripts@29f98b6. I tested it on Martchus#2.

[foursixnine]

@Martchus keep in mind that @openqa points to a different organization, also can you add some description of how it goes? either to the PR template and to the Contributing file

[Martchus]

@Martchus keep in mind that @openqa points to a different organization

That's a very good point. We should maybe avoid using the @-syntax here at all because we don't want to mention any entity on GitHub here. I guess the syntax was inspired by Mergify when we created the ticket. However, unlike Mergify this is not implemented as GitHub application so probably it shouldn't pretend to be one. This is something to be fixed in the scripts repository, though.

I create another PR in the scripts repository and with documentation when we figured out what syntax we'd like to use here.

Maybe we can just leave out the @ and make the : mandatory instead.

[okurz]

@Martchus keep in mind that @openqa points to a different organization, also can you add some description of how it goes? either to the PR template and to the Contributing file

Covered in

• Avoid conflict with GitHub syntax in openqa-clone-…-job-from-pr scripts#295