Please describe the project
Falco is a CNCF-graduated runtime security project.
URL for the project
https://falco.org/
Describe current CI/CD setup
Currently, s390x support is marked as experimental for our drivers since we are not able to run a CI on it: https://github.com/falcosecurity/libs?tab=readme-ov-file#drivers-officially-supported-architectures
At the moment, our s390x CI consists of a single job that just builds our drivers for it through uraimo/run-on-arch-action: https://github.com/falcosecurity/libs/blob/master/.github/workflows/drivers_ci.yml#L196
Describe the primary use case for the Github Action Runner
We will be finally able to both test the build and actually run our drivers tests on s390x.
Also, we might later evaluate to introduce s390x as officially supported Falco architecture (with release artifacts and so on); see the Falco reusable_build_packages workflow, that right now only supports x86 and arm64: https://github.com/falcosecurity/falco/blob/master/.github/workflows/reusable_build_packages.yaml, and the same goes for the build of the official docker images: https://github.com/falcosecurity/falco/blob/master/.github/workflows/reusable_build_docker.yaml
Finally, please do notice that libs repo is not only used by Falco, but there are many more consumers in the wild; namely: IBM itself, Red Hat, and more.
Paste a link to the existing actions workflow file(s) or directory
https://github.com/falcosecurity/libs/tree/master/.github/workflows
We have many more projects, but for now, giving access to the libs repo would be enough for us to quickly improve our support for s390x architecture.
How often do you plan on executing the runner?
Every driver-related commit, that accounts for ~10% of our commits. Let's say an average of once per day.
What is the primary programming language for the project?
C/C++
Please select desired hardware
Account names of the GitHub repo admins that will need access to setting up the runner
FedeDP
Please describe the project
Falco is a CNCF-graduated runtime security project.
URL for the project
https://falco.org/
Describe current CI/CD setup
Currently, s390x support is marked as experimental for our drivers since we are not able to run a CI on it: https://github.com/falcosecurity/libs?tab=readme-ov-file#drivers-officially-supported-architectures
At the moment, our s390x CI consists of a single job that just builds our drivers for it through
uraimo/run-on-arch-action: https://github.com/falcosecurity/libs/blob/master/.github/workflows/drivers_ci.yml#L196Describe the primary use case for the Github Action Runner
We will be finally able to both test the build and actually run our drivers tests on s390x.
Also, we might later evaluate to introduce s390x as officially supported Falco architecture (with release artifacts and so on); see the Falco
reusable_build_packagesworkflow, that right now only supports x86 and arm64: https://github.com/falcosecurity/falco/blob/master/.github/workflows/reusable_build_packages.yaml, and the same goes for the build of the official docker images: https://github.com/falcosecurity/falco/blob/master/.github/workflows/reusable_build_docker.yamlFinally, please do notice that libs repo is not only used by Falco, but there are many more consumers in the wild; namely: IBM itself, Red Hat, and more.
Paste a link to the existing actions workflow file(s) or directory
https://github.com/falcosecurity/libs/tree/master/.github/workflows
We have many more projects, but for now, giving access to the
libsrepo would be enough for us to quickly improve our support for s390x architecture.How often do you plan on executing the runner?
Every driver-related commit, that accounts for ~10% of our commits. Let's say an average of once per day.
What is the primary programming language for the project?
C/C++
Please select desired hardware
Account names of the GitHub repo admins that will need access to setting up the runner
FedeDP