[
https://issues.apache.org/jira/browse/AVRO-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333160#comment-17333160
]
ASF subversion and git services commented on AVRO-3009:
-------------------------------------------------------
Commit 18890afe3d728a0c1ef1f2aba46155c32cf0d567 in avro's branch
refs/heads/master from Ismaël Mejía
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=18890af ]
AVRO-3113: Update enforcer-plugin to version 3.0.0-M3 (#1201)
* AVRO-3113: Update enforcer-plugin to version 3.0.0-M3
It also update other plugin versions to enable the project to build in
more recent JDKs. # Explain why this change is being made
* Revert "AVRO-3009: Fix IP address in GitHub Actions container"
This reverts commit 50676f142fad5d685d9f0e24a7f2e9d01e6eb8e8.
* AVRO-3113: Update github workflows to use actions/setup-java@v2
> 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
> Fix For: 1.11.0
>
>
> 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)
