Apple Silicon (arm64) JFrog CLI binaries fail in ADO extension 2.12.0 (CLI 2.76.1)

[ashokm]

Describe the bug

On Apple Silicon (M-series chips) Azure DevOps agents, pipelines fail when using the JFrog CLI bundled in the Azure DevOps Extension (2.12.0, which ships JFrog CLI 2.76.1). Although the CLI binary path shows arm64, the executable is actually x86_64, causing:

/bin/sh: Bad CPU type in executable

Older versions (e.g., 2.71.3) run correctly. As a result, users must pin to older CLI versions (e.g., 2.71.3), preventing access to newer features, bug fixes, and security updates.

Additional context:

• The extension is behind the official JFrog CLI releases: CLI 2.76.1 was released May 28, 2025, while the latest official JFrog CLI is 2.78.9 (Sep 3, 2025).
• Likely cause: the downloader pulls an x86_64 binary instead of true arm64 for Apple Silicon, breaking pipelines on Apple Silicon.

Current behavior

• Running the JFrog CLI bundled in the extension on Apple Silicon agents fails with the CPU type error above.
• Using JFROG_CLI_LOG_LEVEL="DEBUG" shows the binary is labeled arm64 but cannot execute.
• Pinning to older CLI versions (e.g., 2.71.3) resolves the issue.

Reproduction steps

1. Use an Apple Silicon (arm64) Azure DevOps agent.
2. Use a JFrog task.
3. Run any JFrog command.
4. Observe the error: /bin/sh: Bad CPU type in executable.

Expected behavior

• JFrog CLI runs correctly on Apple Silicon (arm64) agents.
• The extension should download a true arm64 binary, not x86_64.
• Users can use the latest CLI version without pinning.

Azure DevOps extension name and version

New JFrog Azure DevOps Extension, 2.12.0

JFrog CLI version

2.76.1

Operating system type and version

macOS, Apple Silicon (arm64)

JFrog Artifactory version (if relevant)

N/A

JFrog Xray version (if relevant)

N/A

JFrog Distribution version (if relevant)

N/A