[
https://issues.apache.org/jira/browse/AVRO-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264845#comment-17264845
]
ASF subversion and git services commented on AVRO-3009:
-------------------------------------------------------
Commit 6c527e5f6cebd595a14b4b38f47b973a151636fa in avro's branch
refs/heads/dependabot/nuget/lang/csharp/Microsoft.NET.Test.Sdk-16.8.3 from
Michael A. Smith
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=6c527e5 ]
AVRO-3009: Update Status Badges in Readme
Left out in the original switch to actions
> 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)
