Use Docker container for riscv64

[luhenry]

No description provided.

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

[luhenry]

It depends on adoptium/infrastructure#3240

[luhenry]

It is currently blocked by not being able to push the adoptopenjdk/ubuntu2004_build_image:linux-riscv64 to hub.docker.com. See https://ci.adoptium.net/job/centos7_docker_image_updater/397/console for details

[sxa]

This isn't cross compilation so those options aren't likely to work - this PR is trying to run in an emulated environment so from the build process perspective it would be running "natively". Actually that option in the pipelines isn't named very well so what you've got it probably ok and consistent with what we do for arm32 on aarch64 (Although those do execute natively on the hardware)

But as you say it isn't going to work yet until we can push it up.

Why did you select x64 as the host specifically for this?

[luhenry]

But as you say it isn't going to work yet until we can push it up.

Is there a way to manually push the image until the CI is fixed? Given RISC-V isn't an officially supported platform, the necessity for tracking sources of the tools isn't as much a requirement?

Why did you select x64 as the host specifically for this?

Kinda of by default. Happy to use something else if it's any better. The other ones I would see is aarch64 if we have enough machines in that pool (and fast enough) to dedicate to that.

[sxa]

Can we update the commit message on this - I know the option in the pipelines says "crossCompile" but since this is not using a cross-compiler (it's still running the native riscv64 compiler) I'd prefer it to say "Use system emulation" or something along those lines.

[luhenry]

Scaling down the scope of this PR to only using the docker container. We'll see to use x64 host on a follow-up PR.

[luhenry]

Superseded by #864