argb32

Still not fixed..

Is this fixed in latest? Is there a way to track issues like this?

No I'm finding it doesn't do anything other than either 'block' all access to all files or full 'read' to all files.

Following the tutorial this doesn't seem to work? Either they get full access to the whole project or nothing? How do I limit to just reading a subpath? https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide#Giveaccesstoaparticularsubdirectory,butnottheentiretree

For some reason this isn't working at all for me. What am I doing wrong? Keep getting 'xxx.meta' is not changed. Why is it trying to commit a file that hasn't changed?

Using the examples just isn't working? Nothing I do can remove the 'header' and give me a stripped down version of the changed files that the cm ci will accept What's the intended command line use case for this?

I want to limit (filter) the query to the branch so it only shows main branch and not all branches

I can't seem to filter a cm log query by branch? How would I do this? cm log --from=cs:%1 cs:%2 --csFormat="#{changesetid}:{newline}\"{comment}\"{newline}"

What would be the best way to list all the local changes? (including added files) If this isn't possible how about listing what files are in a changelist?

This is specifically with an issue with the replication.. server to server.. no clients 'Error: Only the server administrator can accept a certificate on the server'

Is there a way to install the cer file for the ubuntu 'plasticscm' service user? They don't have a home directory or a login as far as I know, so how are you supposed to install the cer for the service? (since it's not run as a traditional user)

Anyway to do this with the Jenkins 'Selector' interface? I can't seem to set this up. Ideally would like to be able to say update, with resolve conflicts accept head.

Mostly it would have been assets that are modified dynamically, programmatically while working in the editor but only committed once someone explicitly wanted to make the change shared. An example might be something like a cache file, a global material. Though it is understood to avoid this VC noise as much as possible. In any case I see that I can use Gluon and the main Plastic viewer on the same instance of the workspace so for now I'll just do it that way (switch tools). For some reason I thought I was unable to use the Plastic default Client on a workspace setup with Gluon.

It would make sense that there would be an option in the tool - since I imagine the use case is a file you want to be able to be shared but most users changes are local only. There would still be people who would need to commit changes periodically. I guess temporarily hacking the file to not ignore the changes works, though little clunky for a tool like Gluon.

I think there's a misunderstanding, I can edit /commit the hidden_changes.conf.. but I can't commit any files listed in hidden_changes.conf - since I can't seem them.