You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/11/14 05:33:00 UTC
[jira] [Created] (FLINK-20161) Consider switching from Travis CI to
Github Actions for flink-statefun's CI workflows
Tzu-Li (Gordon) Tai created FLINK-20161:
-------------------------------------------
Summary: Consider switching from Travis CI to Github Actions for flink-statefun's CI workflows
Key: FLINK-20161
URL: https://issues.apache.org/jira/browse/FLINK-20161
Project: Flink
Issue Type: Task
Components: Build System / CI, Stateful Functions
Reporter: Tzu-Li (Gordon) Tai
Assignee: Tzu-Li (Gordon) Tai
Travis-CI.com recently announced a new pricing model on Nov. 2, which affects public open source projects: https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
While its a bit unclear if Travis CI repos under {{travis-ci.com/github/apache}} is affected by this, this will definitely affect contributors who fork our repositories and enable Travis CI on their fork for development purposes.
Github Actions seems to be a popular alternative nowadays:
* No limited test time with its hosted builders, if repo is public
* Activation is automatic - one step / click less for contributors to get CI running for their forks
Given that the CI workflows in {{flink-statefun}} is very minimal right now, we propose to make the switch to Github Actions as the efforts to do that should be relatively trivial.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)