Hi, On Tue, Oct 25, 2022 at 4:27 AM Matt Topol <zotthewiz...@gmail.com> wrote:
> I'd prefer not to remove them as there are definitely known users of both > architectures for the Golang libraries. Is CircleCI an option? > No, CircleCI (and DroneIO) is not an option at the moment. CI services which require write permissions for the repositories are not allowed by ASF Infra team! For Linux/Mac ARM64 the options are: 1) Github Actions + self-hoster runner . See https://issues.apache.org/jira/browse/INFRA-23740?focusedCommentId=17612519&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17612519 for more info 2) QEMU emulated, e.g. via https://github.com/uraimo/run-on-arch-action/ (Linux only) For s390x only QEMU is an option, because Github Actions does not support s390x runners. The drawback of 1) is that due to security related concerns a self-hosted runner could be used only as a post-validator, i.e. the CI should run only on approved and merged code. The drawback of 2) is that QEMU emulation is few times slower than native execution. Regards, Martin > > 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 > > >
