avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suraj Acharya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AVRO-1887) set up precommit checks via Apache Yetus
Date Sat, 17 Sep 2016 01:13:20 GMT

     [ https://issues.apache.org/jira/browse/AVRO-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Suraj Acharya updated AVRO-1887:
--------------------------------
    Assignee:     (was: Suraj Acharya)

> 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
>            Priority: Blocker
>
> 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
(v6.3.4#6332)

Mime
View raw message