Hi everybody.

I would like to open a discussion about with continuous integration service
we should use.


I like Travis CI, but after deal with it in the Netbeans project, I start
to think that they aren't a good couple.

There are two Travis CI limits that are a pain in the neck, the log length
limit and the job limit to 50 min. I found that is a common problem and
other Apache projects are migrating his pipelines from Travis or are
thinking about that.

https://cwiki.apache.org/confluence/display/FLINK/2020/03/22/Migrating+Flink%27s+CI+Infrastructure+from+Travis+CI+to+Azure+Pipelines

https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-23+Migrate+out+of+Travis+CI


I would like to suggest two options.

First , the most conservative option, migrate TravisCI pipeline to the
Apache Jenkins infrastructure.

The problem that i see with this option is if we can integrate the Apache
Jenkins infrastructure with GitHub to run the test suite for every
PR/commits and show the results in the GitHub ui.

The other option, is start to test with the GitHub workflows and if they
are better than TravisCI move to use GitHub workflows instead TravisCI.

Reply via email to