1#!/bin/bash 2 3set -ex 4 5# go to the repo root 6cd $(dirname $0)/../../.. 7 8if [[ -t 0 ]]; then 9 DOCKER_TTY_ARGS="-it" 10else 11 # The input device on kokoro is not a TTY, so -it does not work. 12 DOCKER_TTY_ARGS= 13fi 14 15# crosscompile protoc as we will later need it for the ruby build. 16# we build it under the dockcross/manylinux2014-aarch64 image so that the resulting protoc binary is compatible 17# with a wide range of linux distros (including any docker images we will use later to build and test ruby) 18kokoro/linux/aarch64/dockcross_helpers/run_dockcross_manylinux2014_aarch64.sh kokoro/linux/aarch64/protoc_crosscompile_aarch64.sh 19 20# use an actual aarch64 docker image (with a real aarch64 ruby) to run build & test protobuf ruby under an emulator 21# * mount the protobuf root as /work to be able to access the crosscompiled files 22# * to avoid running the process inside docker as root (which can pollute the workspace with files owned by root), we force 23# running under current user's UID and GID. To be able to do that, we need to provide a home directory for the user 24# otherwise the UID would be homeless under the docker container and pip install wouldn't work. For simplicity, 25# we just run map the user's home to a throwaway temporary directory 26 27docker run $DOCKER_TTY_ARGS --rm --user "$(id -u):$(id -g)" -e "HOME=/home/fake-user" -v "$(mktemp -d):/home/fake-user" -v "$(pwd)":/work -w /work arm64v8/ruby:2.7.3-buster kokoro/linux/aarch64/ruby_build_and_run_tests_with_qemu_aarch64.sh