test: add test runner (DEV-3173)

[jnussbaum]

No description provided.

[linear]

DEV-3173 add test runner in import-scripts repo

[BalduinLandolt]

I seem to recall that we once had an issue with timed actions at some point stopping to execute if a repo doesn't get touched regularly (understandably, from GitHub's side of things), so that may be something to look out for.

Also, generally, chron jobs aren't super nice because you don't get immediate feedback, and things may run even if they don't hacve to. So looking into a git hook triggered solution would be nicer, even though maybe a bit more complex. (If you're curious, we have such a setup somewhere in the ARK resolver, I think... but I don't recall the details)

[jnussbaum]

I seem to recall that we once had an issue with timed actions at some point stopping to execute if a repo doesn't get touched regularly (understandably, from GitHub's side of things), so that may be something to look out for.

Also, generally, chron jobs aren't super nice because you don't get immediate feedback, and things may run even if they don't hacve to. So looking into a git hook triggered solution would be nicer, even though maybe a bit more complex. (If you're curious, we have such a setup somewhere in the ARK resolver, I think... but I don't recall the details)

The only thing I found was this: https://blog.marcnuri.com/triggering-github-actions-across-different-repositories. That would mean: in the dsp-tools repo, I send a HTTP request to this repo, with curl -X POST https://api.github.com/repos/dasch-swiss/00a1-import-scripts/dispatches ..., and this would then trigger the workflow, instead of the cronjob. I thought that's an overkill, so I didn't try it...

[BalduinLandolt]

I seem to recall that we once had an issue with timed actions at some point stopping to execute if a repo doesn't get touched regularly (understandably, from GitHub's side of things), so that may be something to look out for.
Also, generally, chron jobs aren't super nice because you don't get immediate feedback, and things may run even if they don't hacve to. So looking into a git hook triggered solution would be nicer, even though maybe a bit more complex. (If you're curious, we have such a setup somewhere in the ARK resolver, I think... but I don't recall the details)

The only thing I found was this: https://blog.marcnuri.com/triggering-github-actions-across-different-repositories. That would mean: in the dsp-tools repo, I send a HTTP request to this repo, with curl -X POST https://api.github.com/repos/dasch-swiss/00a1-import-scripts/dispatches ..., and this would then trigger the workflow, instead of the cronjob. I thought that's an overkill, so I didn't try it...

You wouldn't have to do curl, in the DSP-TOOLS repo you could activate a webhook, which would do the HTTP request for you (see here for an example: https://github.com/dasch-swiss/ark-resolver-data/settings/hooks/80842207?tab=settings ). But if you think it's overkill, we can see how it goes with the cron job.