Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Current PR checks are executed in a private branch based on the scripts in https://github.com/elek/argo-ozone
but the results are stored in a public repositories:
https://github.com/elek/ozone-ci-q4
https://github.com/elek/ozone-ci-03
As we discussed during the community calls, it would be great to use github actions (or any other cloud based build) to make all the build definitions more accessible for the community.
vivekratnavel checked CircleCI which has better reporting capabilities. But INFRA has concerns about the permission model of circle-ci:
it is highly unlikley we will allow a bot to be able to commit code (whether or not that is the intention, allowing circle-ci will make this possible, and is a complete no)
See:
https://issues.apache.org/jira/browse/INFRA-18131
Fortunately we have a clear contract. Or build scripts are stored under hadoop-ozone/dev-support/checks (return code show the result, details are printed out to the console output). It's very easy to experiment with different build systems.
Github action seems to be an obvious choice: it's integrated well with GitHub and it has more generous resource limitations.
With this Jira I propose to enable github actions based PR checks for a few tests (author, rat, unit, acceptance, checkstyle, findbugs) as an experiment.
Attachments
Issue Links
- links to