-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New arcade causes "install-cmake.sh: Permission denied" failures with version 1.0.0-beta.19251.6 #2670
Comments
cc @dotnet/dnceng |
Ack, looking |
Thanks @chcosta ! |
Do you have a repo I can clone @adiaaida and some repro instructions? I tried this on Arcade and it installed the native tools just fine. |
@chcosta This is the PR where we are seeing this failure: https://dnceng.visualstudio.com/internal/_git/dotnet-optimization/pullrequest/1128?_a=overview Repo: https://dnceng.visualstudio.com/internal/_git/dotnet-optimization We run ./build.sh --configuration Release on Linux |
Do you require native tools to be installed for Linux or are you expecting those to be in your Docker image? I suspect that you don't really care about the Linux native tool installation, but this was recently enabled by default. It looks to me like the Linux native tools haven't received the same care that the Windows native tools (likely because of the Docker stuff) and that it's busted in a few ways.
The immediate course of action here is to provide an option to disable non-Windows from native toolset installation. That will need to be followed up with an actual investment in this area. I'll look into preparing a PR for Arcade that will unblock you. If you need changes from Arcade, then you'll have to hack up |
That's right. We do not need the linux native tool installation. |
Filed Native toolset installation scripts between Windows / Linux are not at parity Filed Permit defining native tools installation / OS I'll work on preparing an interim fix |
Thank you so much! |
@adiaaida , #2675 should unblock you |
Do I need to change our yaml/build scripts in anyway to get the behavior? |
Yes, you'll need to the env block to your Linux build step. Something like this... - ${{ if ne(parameters.agentOS, 'Windows_NT') }}:
- script: ./build.sh
--configuration Release
name: build_linux
displayName: 'Build Linux'
condition: succeeded()
env:
DisableNativeToolsetInstalls: true |
thanks! |
We are seeing the following when building the linux legs in the optimization repo with the latest arcade drop:
I believe this is because build.sh was changed with the following code:
Does a file need to be chmod +x'd?
The text was updated successfully, but these errors were encountered: