[
https://issues.apache.org/jira/browse/HDDS-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-2400:
------------------------------
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-q3]
[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:
{quote}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)
{quote}
See:
https://issues.apache.org/jira/browse/INFRA-18131
[https://lists.apache.org/thread.html/af52e2a3e865c01596d46374e8b294f2740587dbd59d85e132429b6c@%3Cbuilds.apache.org%3E]
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.
was:
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-q3]
[https://github.com/elek/ozone-ci-03]
As we discussed during the community builds, 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:
{quote}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)
{quote}
See:
https://issues.apache.org/jira/browse/INFRA-18131
[https://lists.apache.org/thread.html/af52e2a3e865c01596d46374e8b294f2740587dbd59d85e132429b6c@%3Cbuilds.apache.org%3E]
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.
> Enable github actions based builds for Ozone
> --------------------------------------------
>
> Key: HDDS-2400
> URL: https://issues.apache.org/jira/browse/HDDS-2400
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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-q3]
> [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:
> {quote}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)
> {quote}
> See:
> https://issues.apache.org/jira/browse/INFRA-18131
> [https://lists.apache.org/thread.html/af52e2a3e865c01596d46374e8b294f2740587dbd59d85e132429b6c@%3Cbuilds.apache.org%3E]
>
> 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.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
