Add workflow that runs jacocoTestReport on AnkiDroid PR against Anki-Android-Backend PR

[mikehardy]

There was an issue that only turned up in Anki-Android (this repo) CI after merging + releasing an Anki-Android-Backend PR and it would be nice to have a workflow that allowed a PR here that was dependent on a PR there to run our CI targets on the PR here against the result of the backend build there

Just some brainstorming:

• I believe it is possible to have some workflows be callable and provide them arguments, perhaps we could keep the CI workflows fully separate in their repos and just call them - that is have a backend workflow we can call on a specific git commit hash and it will provide a local library we can test?
• maybe in the test workflows here, if there is a local.properties parse it and see if it is local_backend=true, if it is pull a new property that is a git reference (so you can use a branch name) and if it is, then call out to a backend workflow on that hash to build a local rsdroid ?

That would require a final commit in a PR here after launch+release to remove the local.properties but it would still be incremental improvement

...or something

[david-allison]

Iw we use workflow_dispatch + input: string, we can avoid having the commit ref in the local.properties.

Upsides:

• No need to add in 'test' commits

Downsides:

• Reapplying workflows may take a little longer

[mikehardy]

I think a requirement is that it has to be fully automated at least within context of a PR, we can't be fishing out the right string to input, and a test commit while waiting until the real version comes out isn't the worst thing - better than manual workflow runs IMHO

[github-actions[bot]]

Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically

[mikehardy]

I think this has to be in Anki-Android-Backend now that I think about it. Building the backend is a really non-trivial endeavour and it's all set up there. The workflow should pull Anki-Android after the jars are built and run AnkiDroid test / androidTest against the freshly-built artifacts

[dae]

I feel like this would challenging to implement, as long as the two repos are separate. We get 90% there already by using ./build.sh and testing locally, so perhaps that's enough?