-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Pipeline Caching - executable bit is unset after restore #11204
Comments
Fix is in deployment train. CC @fadnavistanmay |
@arjunguha I don't know if it helps, but setting You can enable it this way :
There is a PR somewhere on this github with the details too, not sure how official this is yet, but it works for us on hosted agents with |
Yes, that is rolling out. We've not doc'd it yet because we have microsoft/azure-pipelines-agent#2400. |
Covered by #10925 |
Question, Bug, or Feature?
Type: Bug
Enter Task Name: CacheBeta
Environment
Issue Description
I am building a Rust project using Azure Pipelines and using CacheBeta to cache the
~/.cargo
directory, which contains executable files. When the cache is restored, the executable files do not appear to have the executable permission set.For example, you can see a log here, where the ~/.cargo directory is restored, but the files in ~/.cargo/bin are not executable:
Next step:
I can address this problem by running
chmod a+x ~/.cargo/bin/*
. This seems to not invalidate the cache.Task logs
logs_46.zip
The text was updated successfully, but these errors were encountered: