Traffic Router tests GHA: Include integration tests

[zrhoffman]

This Pull Request

• renames the Traffic Router Unit Tests workflow to Traffic Router Tests
• Makes the Traffic Router Tests GitHub Action run the integration (and external) tests, in addition to the unit tests
• Adds specific paths to the Experimental Traffic Portal v2 workflow's push trigger so it no longer runs on every commit

---

Which Traffic Control components are affected by this PR?

• Automation - GitHub Actions

What is the best way to verify this PR?

Verify that the Traffic Router Tests GHA includes the TR integration tests

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[ocket8888]

Looks like it's having some kind of permissions issue uploading the JUnit reports

You can see this warning and error as annotations in the check run, even though it was successful (which makes sense because the actual tests themselves pass).

[ocket8888]

I'm still seeing the same annotations in the latest run on that JUnit-to-annotation conversion.

Also it's not caching Maven dependencies because it can't find the directory at the end of the run:

Warning: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

[zrhoffman]

I'm still seeing the same annotations in the latest run on that JUnit-to-annotation conversion.

I think that that is because the mikepenz/action-junit-report action is being used in a PR without being in the target branch. See the annotations resulting from the Build and run tests / Execute integration tests (11) workflow run on apache/unomi#512, since they already use mikepenz/action-junit-report.

They don't seem to be using it in any special way, either.

[zrhoffman]

Also it's not caching Maven dependencies because it can't find the directory at the end of the run:

Warning: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.

Fixed in 077d530

[ocket8888]

Well if we can't get annotations on PRs, why have the step for converting JUnit to annotations?

[zrhoffman]

But we can get annotations on PRs. See the annotations generated from the PR I linked above: https://github.com/apache/unomi/actions/runs/3129456290

[ocket8888]

So you're saying that once this is merged it'll add annotations?

Lemme check that out. Or, well, at least check if the warning and error go away.

[zrhoffman]

Switched back to the old action we were using that echoes annotations instead of using the API (I wish more of them did that) in 7483eaa