Xarbrough

Thanks for the reply! Is it possible to configure the merge tools via the CLI? I'd be ok with scripting this with our team, but I can't find any commands for configuring the client. If there's no CLI API I'll try copying the client.conf from a template file and see how that goes.

My team does quite a few different projects and works with multiple contractors, which makes our setup procedure more and more important. I noticed that we constantly have small issues with our merge tool setup. We're using Unity, so we'd like the UnityYAMLMerge tool to be configured for smart merging of scenes and prefabs. This must work for PlasticSCM full GUI and Gluon. By default, the Unity merge tool isn't configured, so every client needs to make sure they set the correct path to the UnityYAMLMerge.exe via the merge tool preferences. More often than not, something goes wrong when copy-pasting the info here or people forget updating their merge tool after a Unity upgrade for example. For my team, it would be easiest if all clients would share the same merge tool settings per repository, since our merge tool is bound to the Unity version, which is also specific to each repository and all developers use the same Unity version per project/repo. What is a feasible way to manage this for my team? If there are no built-in shared settings, would a commandline script that sets up a workspace be the best option or are there other tools to manage the setup for an entire team?

Artists, designers and external contractors in my team have a recurring issue when setting up Gluon: After creating the workspace for the first time, they have to select all folders and files for automatic download: With all our past projects, we always wanted to sync everything (since we are working in Unity). This small setup steps keeps causing confusion and Gluon users repeatedly forget this step and think their workspace is broken and need support to get this right. Would it make sense to make it a default setting to include all folders and files? Or make this configurable at a cloud repository level? I was looking at global configuration files, but it looks like this client setting cannot be shared. Are there other recommendations to handle this setup step? Is it feasible to write a commandline script that artists can run that sets up their workspace and also configures it to automatically load everything?

Thanks, that's perfect!

Thanks again, I've also gone through the security guide and managed to setup what I needed. However, I'm still a little ensure about the overrides in repo specific permissions. As an example, the server has everything denied by default to ensure nobody gets access to anything by accident: And on specific repositories, I want to allow certain permissions, but which of the following override setups do I need? There are 4 possible combinations of overrides/enable/denied and I don't understand when to use which. If the server permission denies every permission and allows none, what is the "correct" way to enable the permission on a specific repository? Only check allowed, leave everything as is (example rmtrigger) Only override denied and uncheck it (example rmrepository) Only override allowed and check it (example rmlabel) Override both, check allowed and uncheck denied (example view) Or should I simply uncheck allow and denied for everything on the server? What happens if nothing is specified? It seems, everyone has access then.

Thanks, I understand the difference now. So, server permissions are the default for all repositories, but I can override permissions per repository. But just to clarify: I have to select each individual permission on each repository where I want to override permissions? So, it's not possible to define a template and assign it to a repository + group with one click? It's not too bad, but ideally, I would simply configure "Group Externals has Access to Repo A", where "Access" would mean a specific set of permissions that I've set up ahead of time and could be the same for multiple repositories.

Until now, our company only used the "administrators" and "developers" group when assigning permissions to our Cloud repositories. We've only assigned users to these different groups and the group permission defaults have been exactly what we needed. However, now I created a new group "Contractors" and assigned new users to the group. I'd like this group to have only specific access to certain repositories. I know, that I can edit permissions on each repository via the Plastic GUI, but it looks like I have to select each repository and tick all of the individual permission checkboxes to make sure the new group has the correct permissions on each repository. Is there a way to share this "permission template" among multiple repositories? In my scenario I simply want to assign users to 3 groups: admins, developers and contractors. Admins should have full access to everything, developers should only read and write to repositories, but not create or delete them, contractors should only read/write on specific repositories.

For my team, when working with Unity, it's important to configure the filetypes.conf file so that Plastic shows a number of files as text, instead of detecting it as binary incorrectly. For example, Unity scene files, prefabs, meta files and asset files. Probably all Unity files should be detected as text since we have Unity serialization set to "force serialize text", which produces readable YAML. What is the best way to configure this for all users on the cloud edition? The docs tell me that it's possible to use the plastic-global-config repository to share the settings between multiple users, but does this work for cloud? If not, I'd love a way for these settings to be configurable either via such a global repository or directly in the cloud website dashboard/backend. An important factor I would want to consider: if I need to change the config at any point, can I do so in a way that is automatically applied to all other users? I think it's not enough to just start from the right settings when cloning a repo for the first time, but I'd want to synchronize settings at a later point in time as well. Or, what are other solutions to these types of problems? My company is still small, but I wonder how larger companies set these things up. Do people write custom install scripts that overwrite local settings files or things like that? Thanks!

Ah right, I think this would make it easier to push/pull projects which I'm working on at the same time, however if I would add all projects to the same sync view, the "Pull visible" button would download changes from all of the referenced repositories, right? In my workflow I usually work on one or two project at the same time (for a couple of weeks) and then move on to a different project. However, sometimes I still need to check out a different project for a few days, so I don't want to delete my sync views in case I need them again quickly. I think, if the last selection would be saved, I could cover all my needs. A "Latest Projects" sync view that is selected by default and pulls the current repositories, then a few other sync views for older projects that are needed from time to time.

I'd appreciate if the Plastic SCM GUI would save the selected sync view (see the blue box selection in the screenshot). Not sure how common this is, but in my team's workflow we usually have a decentralized cloud repository and each developer has a local repo + workspace and sync view for each project. Usually, we only work at a single project a time, so we would select the project's sync view, push/pull changes, then switch to the branch explorer, then to pending changes and back to sync view. This is the cycle repeated multiple times each day. However, when the GUI is closed, the selected sync view is lost and returns to the first sync view in the list, so I have to select e.g. the last item again. It's been bugging a few of our developers lately and I think it wouldn't be too much hassle to save the selection state.

Thanks for those pointers! I've moved to configs, makes sense to have them there in the future, but it didn't help. I then enabled the log, but it didn't show any errors. However, since I needed to get it working again fast, I uninstalled the PlasticSCM plugin and reinstalled it in TeamCity, which solved the issue. Maybe the installation just was corrupted somehow, but now everything is working again fine.

My TeamCity setup with PlasticSCM Cloud Edition has been running fine over the past couple of weeks, but suddenly, without me changing anything about the configuration, TeamCity no longer connects to Plastic. I would have expected some kind of concrete error, but instead, all operations simply hang. For example, when starting a build configuration, it runs "collecting changes" forever, or when I enter the VCS configuration settings and click on "Test Connection", the progress indicator just spins forever. I verified that my Gluon instance on the same machine, running under the same user, has no issues connecting to Plastic cloud. However, I can't get TeamCity to connect again. The only hint about what might be going wrong is this snippet from the log (see the attached file). Is says: Caused by: com.codicesoftware.plastic.core.PlasticException: There was a problem between the IDE and Plastic SCM communication through the console: The pipe is being closed I'm not really sure how to further investigate this. TeamCity logs no further errors, other than ThreadDumps about hanging operations, but they don't contain any exceptions, error or anything specific about Plastic. Any ideas how I can get more information about what is going wrong? teamcity-vcs.log

Is any workaround known? I'm having the same issue, but I don't know how to reproduce it. I simply moved a folder from one location to another as I often do, but this time it throws an error and shows the moved folder as deleted four times. Is there a way to force reset my workspace to the latest changeset in the cloud?

Thanks, I've confirmed it's working now!

I went over the tips and discovered that my issue may be some sort of more specific fluke. At first, nothing seemed to help, I just couldn't get my move detected. However, later, after I submitted the incorrect delete and add, I couldn't reproduce the original issue any longer, no matter which scenario I tried. However, the issue did happen a few times in the past, so I guess it must be something very specific. I'll post again, if I discover anything new.

Thanks for the suggestions, I'll go through the tips to see if anything helps. The files shown in my screen shot haven't actually changed, I only moved them those asset files within Unity by multi-selecting them and dragging them into a new folder. The file content is still the same, but all files are also different from one another (their hashes should be different, in case this could also be causing issues).

I often see plastic showing moved Unity assets as deleted and added instead of as moved. I then right-click on the moved file showing as added to open the "Search moved candidates" dialog. Here, no matter what I set for "Min similarity accepted", nothing shows in the list. What could be going on here? Plastic correctly detects Unity's .meta files as moved, but not the corresponding .asset files. I have text serialization enabled in Unity and also tried explicitly marking .asset files as binary in the filetypes.conf, but it doesn't fix the move detection. Also, it would be nice if I could manually fix these files if the auto detection fails. But I also guess this is what the "Search Matches" option should be doing, but apparently it has some issues.

Hi Carlos, thanks for your response. I've invited your user to our organization Nementic. My team is on the paid Cloud plan. Should I send an email about this issue or where do we best continue our conversation? For the time being, we're using one of our working user accounts on two machines, but of course this is not ideal as the account name should reflect who the developer behind a commit is.

My team is having problems connecting one of our members to our cloud organization. All other accounts work fine. We simply go through the client configuration wizard, then it first asks to login, which works even with the problematic user. It then says "correctly logged in to plasticscm.com" and let's us join our organization. So far everything seems to work fine. We then launch Gluon. However, now a popup appears asking to login again, which then fails despite using the same information as before. When I cancel the failing popup and check the Gluon preferences General tab, I can select "check credentials" which says "Invalid credentials". But the credentials are definitely correct (as mentioned, it worked during the first step and they also work when logging into the browser dashboard). The last few lines of the gluon.debug.log are attached. I've tried to delete or create a connection profile and also played around with the user profile, but nothing changed the invalid credentials message. I've then compared settings to one of the working setups on another machine and couldn't find any differences. Next, I tried the whole procedure using a different account on the same machine and everything worked. We then repeated all of the steps to confirm that it's not only fluke. Finally, I deleted the account that was causing problems and we created a brand new one with a new mail address, but now we have the same issue with this new account. Kind of looks as if we cannot add new accounts, but old ones still work. Any ideas how to debug this? gluon.debug.log

Official recommendations are welcome, e.g. the definitive ignore.conf for Unity projects is a nice resource. However, I believe in the end I know better than the automated tool, so I'd also like this to be optional. Or instead, when creating a new repository, the wizard could offer a ignore.conf template to pick from, or similar, but this silent edit of the existing file is causing confusion in my team (for e.g. designers who do not normally deal with the ignore file).

I don't think you have to download anything. Simply install Unity and Plastic SCM (e.g. Cloud Edition), and then in the Unity Editor Project Settings for the Editor, set version control mode to Plastic SCM. This will enable the feature that draws icons on top of the assets in the Unity project window and lets you checkin file directly in Unity. As far as I know this is already bundled with the Unity installation. There's an Asset Store page titled Plastic SCM that looks like the official plugin, but in fact, the last time I opened it, it was simply an interactive installer for Plastic SCM.

I'm trying to find useful information in the logs, but so far I only found: ERROR PlasticThread - Error when performing background operation: Object reference not set to an instance of an object. ERROR ExceptionHandler - [Application_ThreadException] Unexpected error: Object reference not set to an instance of an object. Also see the attached full log of the few seconds when the error showed. plastic-log.txt

This is now also blocking functionality: On one of our machines, Gluon refuses to work (the popup "An unexpected error has occurred." shows and nothing updates in the workspace, for example. And the error also seems to prevent me from creating new repositories or connecting to a new repo via the client configuration wizard.

Thanks for the info! Too bad, Gluon is one of the best features of the PlasticSCM toolset. I'm also looking into gmaster at the moment, which may be more accessible than the full Plastic GUI.

I've tested GitSync with the full GUI and it worked nicely to connect to a git repository on GitHub.Does the same work with Gluon? I didn't find any documentation about it. It would be fine to configure GitSync via the full GUI and then switch over to Gluon to do checkin/checkout, but so far, Gluon only pushes to the local repository, but not GitHub. I've had similar problems with regular PlasticSCM repositories, when I switched between full GUI and Gluon. So, is GitSync supported with Gluon and how can I set it up?