[build] Run Venice CI with GitHub Actions

[sushantmane]

Run Venice tests on the following matrix:
OS: macOS, Ubuntu
JDK: 11

Run Venice CI with GitHub Actions

While we figure out how we want to run CI with GitHub actions, I think it would be good to have
something up and running in the meantime. With this RB, CI will be run on every commit/pull request.
It triggers one job/OS for unit tests (~42 mins) and one for integration tests/OS (2.30 hours and a bit flaky).

How was this PR tested?

Does this PR introduce any user-facing changes?

• No. You can skip the rest of this section.
• Yes. Make sure to explain your proposed changes and call out the behavior change.

[FelixGV]

Thanks Sushant! Is it normal that the checks show as failed?

[sushantmane]

Thanks Sushant! Is it normal that the checks show as failed?

No, checks should not fail. I know the reason: this PR ('get fetch' part in actions) was designed to work on forks and I need to update it to work everywhere. I'll update it. Thanks.

[FelixGV]

Hi Sushant, would you mind rebasing and retrying this? Curious to see how it goes now. Thanks!

[FelixGV]

I think we need to divide the e2e tests further. One first cut might be to do a split along the lines of:

1. Run all integration tests that match com.linkedin.venice.endToEnd.*.
2. Run all integration tests that don't match com.linkedin.venice.endToEnd.*

Might need to define a couple more test targets in the Gradle build. This seems useful for that: https://mkyong.com/gradle/gradle-how-to-exclude-some-tests/

Are you game to give it a try?

[sushantmane]

I think we need to divide the e2e tests further. One first cut might be to do a split along the lines of:

1. Run all integration tests that match com.linkedin.venice.endToEnd.*.
2. Run all integration tests that don't match com.linkedin.venice.endToEnd.*

Might need to define a couple more test targets in the Gradle build. This seems useful for that: https://mkyong.com/gradle/gradle-how-to-exclude-some-tests/

Are you game to give it a try?

Sorry for the late response. Sure, I'll split e2e tests into two parts. They used to finish in < 3HR and hence I added 3HR timeout. But it seems we've added >25 e2e tests since then.

[sushantmane]

@FelixGV -

1. Run all integration tests that match com.linkedin.venice.endToEnd.*.

Completes in 2h10m

2. Run all integration tests that don't match com.linkedin.venice.endToEnd.*

Completes in 1h

@adamxchen is planning to work on this in the next quarter. In the meantime, should we use this PR?

[FelixGV]

Thanks a lot for the initiative Sushant!! I think we should merge this in, for sure!

In the future, I would like us to reduce the wall clock time by splitting further, and/or deleting redundant tests.

In any case, this is a great start! Thanks again 🙏

[FelixGV]

Tremendous 🤩🍾🙏

[sushantmane]

Thanks for the review. I'll run our internal CI once just to make sure everything else is alright.

[sushantmane]

@FelixGV - Could you please approve the PR again?

[nisargthakkar]

LGTM

[FelixGV]

Thanks a lot! Please make sure to review and clean up the commit message while squashing.

[sushantmane]

Thank you @FelixGV & @nisargthakkar!