You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/01/01 16:01:00 UTC
[jira] [Commented] (AVRO-3009) Use GitHub Actions to CI Avro
[ https://issues.apache.org/jira/browse/AVRO-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17257212#comment-17257212 ]
ASF subversion and git services commented on AVRO-3009:
-------------------------------------------------------
Commit 4467c66e05abf0f3e3ad3570fca4a7769a13533b in avro's branch refs/heads/master from Michael A. Smith
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=4467c66 ]
AVRO-3009 Test in GitHub Actions (#1043)
* AVRO-3009 GitHub Actions
* AVRO-3009: Rat Action
* AVRO-3009: Ruby Matrix
* AVRO-3009: Remove Unused Python Caching
* AVRO-3009: Disable TravisCI
> Use GitHub Actions to CI Avro
> -----------------------------
>
> Key: AVRO-3009
> URL: https://issues.apache.org/jira/browse/AVRO-3009
> Project: Apache Avro
> Issue Type: Improvement
> Components: build
> Reporter: Michael A. Smith
> Assignee: Michael A. Smith
> Priority: Major
>
> The Travis and Yetus based build system has been helpful in getting some kind of CI off the ground for Avro, but it suffers from a number of challenges that haven't been addressed. Based on the fact that other Apache projects such as Airflow use GitHub Actions regularly, I propose to replace the Travis build system with one using GitHub actions, with the following goals and improvements:
> # To run tests in parallel, wherever it makes sense.
> # To isolate tests so that contributors can find relevant logs easily.
> # To only run tests relevant to the current pull request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)