-
Notifications
You must be signed in to change notification settings - Fork 21
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
Permissions of files in working directory aren't preserved when copied #528
Comments
@edigaryev please correct me if I'm wrong but I think we never intended to preserve permissions for non dirty mode (aka when we mount the working directory). In other cases the CLI is just rsyncing/scping files inside the containers/VMs. |
Oh okay, any reason not to use |
Permissions are ignored because when you run your task in Cirrus Cloud, it uses Git to fetch your project directory, and Git is mostly unaware of file permissions, except for the executable bits. Could you explain your use-case a bit better? More specifically, how do you deal with the same issue when running your tasks in the cloud, or do you only use Cirrus CLI locally? |
That makes sense. Yeah you're right, I'm not doing it that way in the cloud; I was using an ssh key not checked into git, which I'll use an encrypted env var for in the cloud. |
Good point, @edigaryev. Let's close it then. I also think there might be an issue with what kind of permissions to do when you run Cirrus CLI on Windows, for example. |
(for posterity I'm guessing a local workaround is --dirty) |
I have a file with permissions
-rw-------
in my working directory, but checking them in the VM they are-rw-r--r--
The text was updated successfully, but these errors were encountered: