Ubuntu arm64 incompatible build scripts

[enescakir]

Description

Some scripts are still x64-specific and set incorrect variables for arm64 images.

For example, install-java-tools.sh still sets JAVA_HOME_*_X64 1 for all architectures, which is incorrect for arm64 images. It also creates an x64.complete file for tool caching 2.

Is this expected behavior, or should the scripts be updated to use the correct architecture?

cc @shamil-mubarakshin

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• Ubuntu Slim
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• macOS 26
• macOS 26 Arm64
• Windows Server 2022
• Windows Server 2025
• Windows Server 2025 with Visual Studio 2026

Image version and build link

Any Ubuntu arm64 images

Is it regression?

Yes

Expected behavior

arm64 images should be built with correct variables (such as JAVA_HOME_*_ARM64) or tool caching files arm64.complete

Actual behavior

For example, install-java-tools.sh still sets JAVA_HOME_*_X64 1 for all architectures, which is incorrect for arm64 images. It also creates an x64.complete file for tool caching 2.

Repro steps

You can search for x64 in ubuntu build scripts

[v-SergeiRadich]

Hi!

We have picked up ARM images from a separate team, so currently they are in "as is" state.

Soon we will update them, including env variables. There will be separate announcement about it, as this is going to be a breaking change for some people.

So far I'm keeping this issue opened for visibility.