Hi, Ah, I forgot that option. Yes, we can use Crossbow for Travis CI. I've created an issue for this: https://issues.apache.org/jira/browse/ARROW-18316
Thanks, -- kou In <f4e1551f-fd04-6cda-38de-6292f45e5...@python.org> "Re: [DISCUSS] Migrating away from Travis-CI" on Tue, 25 Oct 2022 09:15:56 +0200, Antoine Pitrou <anto...@python.org> wrote: > > We can turn those builds into Crossbow builds. > QEMU is not reasonable given the already long build times. > > Regards > > Antoine. > > > Le 25/10/2022 à 03:26, Matt Topol a écrit : >> I'd prefer not to remove them as there are definitely known users of >> both >> architectures for the Golang libraries. Is CircleCI an option? >> On Mon, Oct 24, 2022 at 9:13 PM Sutou Kouhei <k...@clear-code.com> >> wrote: >> >>> Hi, >>> >>> https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations >>> >>>> On November 2nd, 2020, Travis-CI announced the end of >>>> unlimited support for open source projects. >>>> >>>> Infra is therefore moving our CI offerings away from >>>> Travis-CI in order to keep our builds pipeline >>>> cost-effective >>>> >>>> Deadline: December 31st 2022 >>>> >>>> Infrastructure is moving ASF projects away from using >>>> Travis-CI at the end of 2022. >>> >>> We're using Travis CI for CI on ARM and s390x. What should >>> we do for CI on these architectures? Do we just remove them? >>> Or do we prepare new CI on these architectures? >>> >>> >>> Thanks, >>> -- >>> kou >>> >>
