Apache Arrow #107

Please describe the project
Apache Arrow defines a language-independent columnar memory format for flat and nested data, organized for efficient analytic operations on modern hardware like CPUs and GPUs.

URL for the project
https://arrow.apache.org/

Describe current CI/CD setup
The Arrow project is using GitHub actions. In the past (long time ago) we used to have Travis with s390x runners but since Travis changed licensing we removed them.

Describe the primary use case for the Github Action Runner
Building and testing software on s390x and ppc64le architectures.

Paste a link to the existing actions workflow file(s) or directory
https://github.com/apache/arrow/tree/master/.github/workflows

How often do you plan on executing the runner?
On our specific case would be nightly and on-demand, when we are working on possible related issues. We could target the job to be quite specific so it only runs when strictly specified on specific PRs/commits. But at least once a day.

The jobs runs should take from 20 minutes to 1 hour, depending on the build flags in use and what components are built and the capacity of the build host. Without an initial runner and some validation it is difficult to estimate how long it will take.

What is the primary programming language for the project?
C++

Please select desired hardware

• Power 9 (ppc64le)
• IBM Z / LinuxONE (s390x)

Account names of the GitHub repo admins that will need access to setting up the runner
reanguiano will be setting up the runner, but these are my ASF Infra teammates that should also have the same level of access:

gmcdonald
Humbedooh
cwlls
bobthomson70
clambertus
dfoulks1