Thanks for bring this up @Philipp Dallig <[email protected]> This is also an issue for me, but I don't know what other better options we have, maybe we can use apache's jenkins platform, but it may be very slow. Or we can check what other apache project use for CI
Philipp Dallig <[email protected]> 于2020年11月21日周六 下午9:13写道： > Hi Folks, > > I think that travis-ci.org and travis-ci.com can no longer be used for > our CI tests. Due to a restriction for open source builds > (https://twitter.com/geerlingguy/status/1324480667984498689) I have > migrated my Zeppelin fork from travis-ci.org to travis-ci.com. > > Last week I received 10000 credits for starting travis-ci.com build > jobs. Unfortunately these credits are used up very quickly due to the > many and long tests. I used up these 10000 points within one day. > > Some facts from the timeline: > - In May 2018 Travis CI announces open source project migration to > travis-ci.com > ( > https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps > ) > - On Nov 2, 2020: Travis CI announces new pricing model, effectively > ends generous open source offering. > (https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing) > - December 31, 2020: Travis-ci.org will be put into read-only mode. > ( > https://docs.travis-ci.com/user/migrate/open-source-repository-migration/#frequently-asked-questions > ) > > > Do we have a plan for migration, and if so, what is our plan? > > Is anything planned by the Apache Foundation? > > I would prefer a CI platform where a new user with a pull request does > not have to do a CI setup or a setup with only a few steps. Of course, a > new CI platform should be as transparent as possible. > > With kind regards > Philipp Dallig > > -- Best Regards Jeff Zhang
