Thierry
-
Posts
3 -
Joined
-
Last visited
Posts posted by Thierry
-
-
Hi Carlos,
Indeed, I forget to explain our situation.
We are working on Unreal Engine, so all binaries are added in the lock rules via the cloud interface. So this issue only concerne benaries files.
So when we change something in Unreal, it asks us if we want to checkout the file or if we want to make it writable. If we do so, as long as we don't update the workspace, the status of that file in plastic client is "changed" and it is not lock for other users. But as soon as we update the workspace, the status change to Checked-out and it's lock for everyone.What I want is to let that file as writable/change without it being locked, except if we manually checkout it.
-
Hello,
We have a big issue for our workflow. Regularly, we set a file as writable because of some testing or whatever. Our issue is that when a file is mark as Writable and we update our workspace, evey writable files will be automatically checked-out. So even we do some stuff that doesn't need to be push and will be revert, we block everyone else that wanted to work on those specific file.
Is there a way to setup plastic so it won't continue to automatically checkout writable files ?
Thanks,
Thierry
Disable auto checkout on writable files when updating workspace
in Installation and configuration
Posted
well, if it's not normal this is very strange as I don't think we have an atypical workflow.
It happens to all changed items.
We only use Plastic SCM software. Nobody use Gluon. The only thing that we are doing from Unreal Editor directly is checking out items when we start editing them (or choose to made them Writable).
Best,
Thierry