From: firstname.lastname@example.org To: email@example.com Subject: [ruby-core:95277] [Ruby master Misc#16234] Enabling ARM 64/32-bit cases by Drone CI Date: Tue, 08 Oct 2019 11:25:58 +0000 (UTC) [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Issue #16234 has been updated by jaruga (Jun Aruga). > That's a nice feature. Possibly we can drop Drone to simplify the situation if we can give up arm32 support (not sure). Yeah, it's a nice feature. We can drop Drone CI, if Travis works well with "arch: arm64". We might be able to run arm32 (ARM 32-bit) using multilib on arm64 (ARM 64-bit) on Travis too, as we have already been running i686 (Intel 32-bit) case on x86_64 (Intel 64-bit) on Travis. I am still thinking about the possibility to check Solaris and FreeBSD and etc case at a pull-request timing with SSH Runner on Drone CI. > if we can give up arm32 support (not sure). I think arm32 is still popular for users, at least more than i686 (Intel 32-bit). Because of the supported architectures for Linux distributions, Raspberry_Pi and the market share. Let me explain it one by one. ### Linux distributions For example Ubuntu is supporting arm32, providing the container image. > https://hub.docker.com/_/ubuntu > Supported architectures: (more info) > amd64, arm32v7, arm64v8, i386, ppc64le, s390x Fedora project is supporting arm32 too. > https://hub.docker.com/_/fedora > Supported architectures: (more info) > amd64, arm32v7, arm64v8, ppc64le, s390x ### Raspberry Pi > https://en.wikipedia.org/wiki/Raspberry_Pi > https://www.raspberrypi.org/blog/raspberry-pi-2-on-sale/ According to the Raspberry Pi wikipedia page, the Raspberry Pi version 1.1 is the last model for 32-bit, and the announcement was 5 August 2015. When I discussed about use cases of ARM 32-bit in Fedora project, someone said "the Raspberry Pi performs quite badly as a 64-bit device for the moment, I've used it with Fedora armv7hl instead of aarch64." according to the email thread: https://firstname.lastname@example.org/message/Q742AVVBR6W6RTSVRYDSSGVKFOM3XTEF/ ### Market share In 2017, armv7 (ARM 32-bit) was 98.1% in total Android device market share. https://android.stackexchange.com/questions/186334/what-percentage-of-android-devices-runs-on-x86-architecture/202022#202022 I would like to hear other people's opinion about how much ARM 32-bit CPU is used currently. I assume people working at ARM are in Ruby project, and they have current market share data about ARM 32-bit. > I'm neutral about introducing the Starlark. While it simplifies duplications in the build config, obviously current maintainers are not familiar with the language. Other CI systems are achieving the same thing by either YAML alias or a built-in matrix syntax. Doesn't Drone support any of them? You are right. The Starlark way is not great for Ruby project. I would close the pull-request. I have not investigated about the YAML alias in Drone CI yet, and I could not find the matrix syntax in it. ---------------------------------------- Misc #16234: Enabling ARM 64/32-bit cases by Drone CI https://bugs.ruby-lang.org/issues/16234#change-81953 * Author: jaruga (Jun Aruga) * Status: Closed * Priority: Normal * Assignee: ---------------------------------------- Currently ruby project has 4 CIs on GitHub. 1. Travis CI: linux cases with flags and compilers. 2. GitHub Actions: macros, windows, ubuntu 3. Wercker: Ruby JIT cases 4. Appveyor: windows I like to suggest 5th CI: Drone CI for ARM 64/32-bit cases. Drone CI supports native the ARM 64/32 bit environments. Have you used Drone CI? I tried to use both Drone CI and Shippable CI supporting ARM. My impression for Drone CI is quite good. Great user experience and user interface. Shippable CI was not so good for some reasons. Drone CI have not only linux ARM 64/32 bit environments on DockerRunner mode (= using container for CI like Wercker), but also freebsd, netbsd, openbsd, dragonfly (?) and solaris environments on ExecRunner (= maybe running commands directly without container) mode according to the following documents. * https://exec-runner.docs.drone.io/configuration/platform/ * https://docker-runner.docs.drone.io/configuration/platform/ Is it exciting isn't it? We can check ARM issue at a pull-request timing. Here is the example. The content is almost same with wercker.yml except JIT option. "ruby/3" is failed on the latest master branch, but "ruby/2" arm64 case is succeeded on old master branch. https://cloud.drone.io/junaruga/ruby/3 https://github.com/junaruga/ruby/blob/feature/ci-arm/.drone.yml https://cloud.drone.io/junaruga/ruby/2 Here is the pull-request as an example. https://github.com/ruby/ruby/pull/2520 .drone.yml is the file to manage the CI cases. But when you see most of the YAML parts between ARM 64-bit and 32-bit cases in .drone.yml is same. In case of .traivs.yml, we are using YAML anchor (&) and reference (*) feature effectively. But in case of .drone.yml I am not sure we can still use it beyond the "---" separator. Luckily Drone CI started providing the alternative .drone.star file by Starlark language. https://docs.drone.io/starlark/overview/ https://blog.drone.io/create-pipelines-using-starlark/ Enabling Drone CI is quite simple. Just go to https://drone.io/ , then register and enable target repository. UI is quite good. Pros * We can check ARM 64/32-bit cases, and possibly freebsd and solaris cases too. * It's for free. * Each developer can debug ARM cases on their forked repository. * Customize easily. I see .travis.yml is used effectively. Cons * Have to manage additonal file .drone.yml or .drone.star. But first, I want to ask you. Are you interested in using Drone CI for Ruby project? -- https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-10-08 11:26 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> 2019-10-03 18:41 ` [ruby-core:95201] " jaruga 2019-10-03 19:20 ` [ruby-core:95203] " jaruga 2019-10-03 19:24 ` [ruby-core:95204] " takashikkbn 2019-10-03 21:14 ` [ruby-core:95206] " takashikkbn 2019-10-03 22:48 ` [ruby-core:95209] " jaruga 2019-10-03 23:56 ` [ruby-core:95212] " mame 2019-10-07 22:30 ` [ruby-core:95270] " jaruga 2019-10-07 22:41 ` [ruby-core:95271] " jaruga 2019-10-08 2:17 ` [ruby-core:95275] " takashikkbn 2019-10-08 11:25 ` jaruga [this message] 2019-10-08 13:33 ` [ruby-core:95278] " takashikkbn 2019-10-08 14:56 ` [ruby-core:95279] " jaruga 2019-10-15 20:16 ` [ruby-core:95346] " jaruga 2019-11-04 14:31 ` [ruby-core:95667] " jaruga 2019-11-06 17:11 ` [ruby-core:95725] " jaruga 2019-11-06 19:09 ` [ruby-core:95726] " jaruga 2019-11-06 19:26 ` [ruby-core:95727] " jaruga 2019-11-06 22:07 ` [ruby-core:95729] " eregontp 2019-11-06 22:08 ` [ruby-core:95730] " eregontp 2019-11-06 22:12 ` [ruby-core:95731] " eregontp 2019-11-07 14:37 ` [ruby-core:95742] " jaruga 2019-11-07 20:43 ` [ruby-core:95748] " jaruga 2019-11-08 18:09 ` [ruby-core:95763] " jaruga 2019-11-11 17:31 ` [ruby-core:95796] " jaruga 2019-11-12 18:05 ` [ruby-core:95818] " jaruga 2019-11-21 15:52 ` [ruby-core:95906] " jaruga
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-list from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.ruby-lang.org/en/community/mailing-lists/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [ruby-core:95277] [Ruby master Misc#16234] Enabling ARM 64/32-bit cases by Drone CI' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/ruby.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).