You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running into problem shipping a custom ADO build task which wraps calling a platform specific executable. The extension bundles in it a Rust built native binary for Windowsx64, Mac (x64/arm64), and Linux x64. On mac, the agent machine doesn't have permission to run chomd +x on the binary when running as an "install" taask.
How do other install tasks handle this if the underlying extension package is using Zip, which doesn't preserve the executable bit for Linux/Mac binaries?
The text was updated successfully, but these errors were encountered:
Hi @kyle-rader-msft, thanks for reporting.
Could you please share detailed information about how you build that binary and is this Mac related issue only?
I'm running into problem shipping a custom ADO build task which wraps calling a platform specific executable. The extension bundles in it a Rust built native binary for Windowsx64, Mac (x64/arm64), and Linux x64. On mac, the agent machine doesn't have permission to run
chomd +x
on the binary when running as an "install" taask.How do other install tasks handle this if the underlying extension package is using Zip, which doesn't preserve the executable bit for Linux/Mac binaries?
The text was updated successfully, but these errors were encountered: