JanetGilbert Posted January 23, 2019 Report Share Posted January 23, 2019 How do I set up the cloud edition so that artists can use exclusive locks but coders don't have to? I want it to give an error if a developer tries to push a checkin to the server that tries to change a file that an artist has checked out. Is this possible? I see a lot of references to lock.conf in the documentation, but I'm not sure if this is needed for the cloud. I've set up the cloud admin page to have lock rules for the repository in question, but it didn't create a lock.conf file on disk... was it meant to? Link to comment Share on other sites More sharing options...
calbzam Posted January 24, 2019 Report Share Posted January 24, 2019 Hi, From your organization panel at "cloud.plasticscm.com" you can configure custom lock rules for your repos based and path, file extension...You don't need to manually create a "lock.conf". This is only necessary for hosted servers. For cloud servers, you just need to use this panel If you are going to use locks, you have to follow a centralized workflow, users directly committing to the central cloud server. If the developers are following a distributed workflow (push/pull branches from a local repo), the locking is not going to work. More info regarding the locking workflow: https://www.plasticscm.com/book/#_locking_avoiding_merges_for_unmergeable_files Regards, Carlos. Link to comment Share on other sites More sharing options...
JanetGilbert Posted January 29, 2019 Author Report Share Posted January 29, 2019 Thanks. How do I ensure I am following a centralized workflow? Link to comment Share on other sites More sharing options...
calbzam Posted January 29, 2019 Report Share Posted January 29, 2019 Hi @JanetGilbert Centralized workflow: Your Plastic workspace is pointing directly to a cloud repository. You are not using local repos. Regards, Carlos. Link to comment Share on other sites More sharing options...
JanetGilbert Posted January 29, 2019 Author Report Share Posted January 29, 2019 I have a repository "MyProj@local" pointing to "MyProj@MyCompany@cloud" I presume you mean I need to get rid of MyProj@local? How do I do this? I set it up with the default settings. Link to comment Share on other sites More sharing options...
JanetGilbert Posted January 29, 2019 Author Report Share Posted January 29, 2019 I think I figured it out. If you set up the project as the install wizard suggests, you get a distributed workflow. This is very confusing. Link to comment Share on other sites More sharing options...
calbzam Posted January 30, 2019 Report Share Posted January 30, 2019 The default workflow for the Plastic GUI is working distributed (no locks) and the default workflow for Gluon is working centralized (with locks). But you can also configure the Plastic GUI to work fully centralized with locks. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now