David Cañadas

Well, the action to take (feature request, workaround, ticket...) it's up to you guys I think. I don't care the method, but it looks there is something missing in your command line client... So, may I understand you'll take care of it, or do you need me doing something specific?

Is there any reason why this question is not being attended?

Hi, We have a trigger that runs some stuff based on the user that requested a Code Review. However, now we are interested in assigning CRs to groups instead of users, hence we need to unwrap the group into the list of member users conforming this group. Unfortunately, we didn't manage to find the way to get such list. Can you please guys provide us with the command line to list the Plastic SCM users that belong to a particular Plastic SCM group?

That's dope @calbzam! However the interface is not that friendly compared to other solutions (at least for the documented part). What I would expect of that system (based on the requirements of my DevOps team): * To be able to provide a maximum number of revisions per file type and/or per file path. * The Plastic SCM server to take care automatically of archiving data based on the provided setup. Are there any plans to provide that (or similar) interface?

The question is self explanatory Asking whether there is (or will be) a plugin for Maya like the one P4 has. Thank you!

On demand is ok, I was trying to save some time

Exactly.

Hi, we are planning to block access to our cloud server by IP. We need to know whether you the Plastic SCM team need your IP to be whitelisted (in that case, we need your IP to add it to the list).

Thank you!

Hi! A few years ago I proposed this "Collaborative merges" feature while working at Digital Legends. It was even mentioned in your Twitter account The idea behind Collaborative Merges is to help resolving merge conflicts that involve more than one person, something that occurs quite often in medium to big projects. Now, merges requiring more than one person to resolve conflicts forces the one running the merge operation to ask everyone involved to either come to his/her spot or connect remotely to resolve conflicts. Besides that, your workspace is locked until the merge operation is either completed or undone. As the Plastic merge status is locally stored as a bunch of files, would be great if such state can be sent to another user, so you can start the merge, resolve just your conflicts, and send the merge over to the next user, undo your changes and continue working normally with your workspace meanwhile. Of course, some things have to be settled up, for instance the collaborative merge instance shall block the branch target, or to use a temporary or child branch to reduce the impact within the merge operation. I would like to know whether is this still a thing or has been discarded/postponed Thanks!

Hi, just wanted to know if there is any ETA to get partial workspaces on the Plastic GUI client. Thank you!

Can I ask how it works in Gluon? Is it just checking out the files after checking them in, or it is a command line argument passed when the checkin operation is run?

I think I've explained myself incorrectly. When I say "my mergebot" I am not saying a Plastic SCM MergeBot instance, I mean my own mergebot (written by me). There is no error at all, but my mergebot received an exit code different from 0 even though the merge operation did succee. I am going to log the exit code and if it happens again, I will contact you back. Thank you!

Hi, the users that asked me for this don't use Gluon and I'm pretty sure they're not open to using it.

Hello, my merge bot raised an error running a regular server-side merge operation which actually was successful. After double-checking the merge bot code, I've seen that the only point in which I can get this error from the merge bot is running cm.exe and getting and exit code different from zero. I couldn't catch the error then, and further merges did work as expected. The cm.exe command line for the operation was: cm.exe merge "<SOURCECHANGESETSPEC>" --merge --mergetype=try --automaticresolution=eviltwin-src;changedelete-src --to="br:<DESTINATIONBRANCHSPEC>" --machinereadable --nointeractiveresolution The cm.exe output for the operation was: FILE_SRC <SOURCEFILESPEC> CHANGESET <DESTINATIONCHANGESETSPEC> (mount:'/') (actual data omitted for confidential purposes). The file is a binary file (.uasset). I've repeated the operation using the same command line and source changeset to a new branch with the destination state ATM and it worked perfectly. The exit code after running this manual test was 0 (EXIT_SUCCESS), which is not compatible with my merge bot to fail. As mentioned above, further merges worked without problems. Hence, I would like to ask you for the full list of the cm.exe exit codes to be able to manage them correctly within my merge bot. Thank you!