Search the Community
Showing results for tags 'configuration'.
Found 3 results
I have created a serveralias.conf that works when installed in my plastic4 user directory per https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide.shtml#Chapter13:Supportalternativeconnectionstothesameserver However, now I am trying to create a global configuration so that all users get this by default. I created a repo, plastic-global-config, such that I have the following file plastic-global-config/allrepos/serveralias.conf *This does not work* After restarting my plastic client, it seems that the global serveralias.conf has no effect. Thanks in advance.
Since Gluon defaults to have no files/folders added to your workspace, and seeing as there's probably a reason why someone is adding a workspace (i.e. to get files/folders), why not put you right into the configuration screen? This has stumbled a few people who didn't know why they weren't pulling any files and it's annoying to resolve it remotely since you have to go step-by-step verifying everything they've done.
I posted this topic in the user voice system, but wanted to add some details. http://plasticscm.uservoice.com/forums/15467-general/suggestions/3847356-integrate-the-repository-configuration-plastic-co Having your client configured for only a SINGLE plastic server is really a pain - especially since I have 2 active servers I wan't to pull work from. And, each has it's own bug tracking link/setup, which has to be reconfigured every time I want to switch from one to the other. I'd like to be able to configure multiple servers each with their own preferences and be able to switch between them from the Plastic GUI. - as shown in the attached image. I don't think any of the older tools (CVS, SVN, VSS, etc) restrict the user to a single server, or require re-configuration to connect to a different one.