THRIFT-5564: setup compiler-building github action [skip ci]

[jimexist]

setup a basic github action. this is part of THRIFT-5564 but does not completely close it yet.

• Did you create an Apache Jira ticket? (not required for trivial changes)
• If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
• Did you squash your changes to a single commit? (not required, but preferred)
• Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?
• If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

[jimexist]

cc @Jens-G i guess this needs to be enabled after the merge - for now i can't see from the actions tab whether it's working or not

[ctubbsii]

cc @Jens-G i guess this needs to be enabled after the merge - for now i can't see from the actions tab whether it's working or not

You should be able to see if it's working in your fork.

[jimexist]

cc @Jens-G i guess this needs to be enabled after the merge - for now i can't see from the actions tab whether it's working or not

You should be able to see if it's working in your fork.

thanks for the pointer - it's https://github.com/Jimexist/thrift/actions/runs/2237581561 and working for now

[jimexist]

cc @Jens-G i guess this needs to be enabled after the merge - for now i can't see from the actions tab whether it's working or not

You should be able to see if it's working in your fork.

thanks for the pointer - it's https://github.com/Jimexist/thrift/actions/runs/2237581561 and working for now

with that passed i plan to leave this pull request as is and put future work in subsequent pull requests to make the change / shift incremental.

my current plan is to have several steps:

1. enable thrift compiler building in ubuntu (this PR)
2. enable thrift compiler building in macOS and windows
3. use artifact sharing to share the pre-built compiler, and create subsequent library building workflows per language - this is unlike the current setup in travis where a monolithic docker environment has to be setup
4. if that goes smoothly, have a final cross test runner that combines all the built cross test runners

[ctubbsii]

This only partially accomplishes the task described in the JIRA. But, I think that's okay, because you need the GitHub Actions to be enabled, which this will do, in order to validate future changes that are more complex. However, this needs to run on PRs as well as push, in order to be useful.

[jimexist]

@ctubbsii thanks for the review - i guess it's turned on now 🏁