-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travis CI: Now supports builds on arch: ppc64le and s390x #2016
Comments
I think this is really interesting, but unfortunate its only specific ubuntu versions. I wonder if we could retire some of our hosts in favour of Travis? |
I'm not even sure I'd class ppc64le and s390x as alpha as AFAIK Travis have never announced these. |
@sam-github I know we (IBM) are working with Travis on support for these platforms. I'm not sure we'd want to do something specific for PPC/s390 versus what we do on other platforms. The proposal to use docker (If @rvagg can get it working consistently ) seems a bit more interesting. I also agree with @richardlau that we'd want to let it bake a bit more before betting on it. |
I agree with waiting, its too cutting edge to commit to now. wrt.
I didn't suggest doing something specific for ppc/s390. It is the lack of architecture, OS, and distro diversity on Travis (and CI-as-a-service generally) that forces us to maintain so much diversity in node CI. If Travis gains diversity and gets it stable, then we can run more jobs on Travis generally, not just specifically for a couple archs, and x64 (existing on Travis), arm, ppc, and s390 seems like its approaching pretty close to covering our arch varieties. |
Nothing planned to do here at the moment, so closing. |
Travis has now announced these as alpha 🎉: https://blog.travis-ci.com/2019-11-12-multi-cpu-architecture-ibm-power-ibm-z |
This is in alpha but it seems to work: https://docs.travis-ci.com/user/multi-cpu-architectures
.travis.yml
arm64
,ppc64le
, ands390x
currently seem to default to Bionic http://releases.ubuntu.com/18.04The text was updated successfully, but these errors were encountered: