[jira] [Commented] (AVRO-1887) set up precommit checks via Apache Yetus

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
Report Content as Inappropriate

[jira] [Commented] (AVRO-1887) set up precommit checks via Apache Yetus

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/AVRO-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867146#comment-15867146 ]

Suraj Acharya commented on AVRO-1887:

Created a pull request here : https://github.com/apache/avro/pull/196
I have added some comments in the pull request.
Please test it and let me know your comments.

> set up precommit checks via Apache Yetus
> ----------------------------------------
>                 Key: AVRO-1887
>                 URL: https://issues.apache.org/jira/browse/AVRO-1887
>             Project: Avro
>          Issue Type: Task
>          Components: build, community
>            Reporter: Sean Busbey
>            Assignee: Suraj Acharya
>            Priority: Blocker
>         Attachments: AVRO-1887-0.patch, AVRO-1887-1.patch, AVRO-1887-2.patch
> The lack of automated checks for things like doing a full build is negatively impacting my ability to do timely reviews. We should leverage the work done by other communities and get precommit checks going with Apache Yetus ([ref Apache Yetus Precommit|http://yetus.apache.org/documentation/0.3.0/precommit-basic/])
> Yetus has built in support for using Docker as a containerized build environment ([ref docs|https://yetus.apache.org/documentation/0.3.0/precommit-advanced/#Docker_Support]), but I don't know if we can use the one we have directly or if we'll need to do some refactoring.
> Implementing this will ultimately require a committer (so that they can make changes to builds.apache.org), but a non-cmmitter can get the bulk of the work done by managing to do local yetus checks with the docker feature active.

This message was sent by Atlassian JIRA