For this old topic running CI services for Big endian arches, I just share the current tips. Until recently Travis CI with the native s390x was a candidate. Though it's not really free for every open source project, if your project can pay the fee, it might be a candidate. https://blog.travis-ci.com/2019-11-12-multi-cpu-architecture-ibm-power-ibm-z Cirrus CI persistent workers feature to enable the CI on your own self servers as a CI running host. The upstream Ruby project is considering that they will try this way. https://github.com/cirruslabs/cirrus-ci-docs/issues/263#issuecomment-746900845 https://medium.com/cirruslabs/announcing-public-beta-of-cirrus-ci-persistent-workers-7327a38004be https://cirrus-ci.org/guide/persistent-workers/ If your project can pay the server fee, you can try s390x VM from a free trial. Then you might be run the VM with above Cirrus CI persistent workers/ https://developer.ibm.com/components/ibm-linuxone/gettingstarted/ On Tue, Nov 13, 2018 at 2:46 PM Jun Aruga <jaruga@xxxxxxxxxx> wrote: > > I just created the topic on Travis community page. > https://travis-ci.community/t/multiarch-testing-tips/862 > > Jun -- Jun | He - His - Him _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
