roadrunner Posted December 19, 2011 Report Share Posted December 19, 2011 In version 4.0.237.2, the GUI has an option to Checkout and another to Checkout Exclusive. In either case, other clients cannot see this checkout status when connected to the same shared repository. I'm assuming this is a bug as there's no other reason for Checkout Exclusive is there? Is there a planned fix coming for this soon? This seems to be the case even if the revision type is set to Binary (on a .JPG file for example) Link to comment Share on other sites More sharing options...
deanaug Posted December 19, 2011 Report Share Posted December 19, 2011 (We are still using 3.0, not sure how 4.0 works in comparison). When you say other clients don't "see" the checkout status, do you mean it doesn't show up when displaying All checkouts (or 4.0 equivalent), or other users are also able to check out the file after the exclusive checkout? If either/both is true, sounds like this may be a bug in 4.0. Link to comment Share on other sites More sharing options...
manu Posted December 19, 2011 Report Share Posted December 19, 2011 Hi all, well it's not a bug... It's a pending thing to do.... It's in our ToDo list... we will do it! Link to comment Share on other sites More sharing options...
deanaug Posted December 19, 2011 Report Share Posted December 19, 2011 Hi all, well it's not a bug... It's a pending thing to do.... It's in our ToDo list... we will do it! That makes it a "feature" then. Thanks for the info Manu!!! Link to comment Share on other sites More sharing options...
manu Posted December 19, 2011 Report Share Posted December 19, 2011 That makes it a "feature" then. Hehehe I guess that! I'm not sure if roadrunner thinks the same Link to comment Share on other sites More sharing options...
roadrunner Posted December 19, 2011 Author Report Share Posted December 19, 2011 It's a blocking issue to me.... can't switch over without it. Any idea on timeframe? Now that I've been using 4.0, I really don't want to use 3 just for this feature. We'll have to use SVN instead of Plastic. (Hopefully if I make you cringe, it'll up the priority level.) Link to comment Share on other sites More sharing options...
manu Posted December 20, 2011 Report Share Posted December 20, 2011 Hi roadrunner, You are going to use the exclusive checkout for binary or text files? Do you know that plastic can handle the workflow in a single branch in a very easy way performing merges, right? We have more priority tasks right now, are you a CommunityEdition user or do you have purchased any support/product licenses? Regards, Manu. Link to comment Share on other sites More sharing options...
roadrunner Posted December 21, 2011 Author Report Share Posted December 21, 2011 Exclusive use is desired for both Binary and Text files. Binary files such as graphical resources, and some text files. Most everything can be merged later, but there are times where it's desirable to lock a file from shared use in the shared repo. Some files are simply more painful to merge than others...if you know that ahead of time, lock it. Also, some sections might be in for a big refactor (15+ year old legacy codebase) If you plan on a refactoring a few units, it's best to lock those to prevent merging issues. It simply puts a tool in the developers hands to let them decide when a lock will save future headache. Community Edition user. Link to comment Share on other sites More sharing options...
manu Posted December 22, 2011 Report Share Posted December 22, 2011 Hi roadrunner, I totally understand you, in that cases the exclusive checkout is very useful... I can only say that we are going to develop it, but right now there are things with more priority... We are a small team and we have to dismiss (for some time) some tasks.... Link to comment Share on other sites More sharing options...
psantosl Posted December 29, 2011 Report Share Posted December 29, 2011 We need exclusive checkout for several uses right now. You could "easily" simulate it using before-checkout triggers, having some sort of global list, but it takes some time to implement. This is exactly what we want to do. My goal is to have it up and running before the end of January, but we've really a lot of things on the table right now. My plan is to modify a little bit the "checkout" operation so that "exclusive checkout" continues making sense even on distributed environments... so, have some sort of "central server" to control "exclusive checkouts"... It will be optional so teams can choose whether they want to work on "checkout mode" or not. Link to comment Share on other sites More sharing options...
Uvaavu Posted January 3, 2012 Report Share Posted January 3, 2012 Damn, this feature was one of the ones on my list that made Plastic an evaluation candidate. Any roadmap for the order in which things missing from 4 that were in 3 will be added back (like this)? Link to comment Share on other sites More sharing options...
psantosl Posted January 8, 2012 Report Share Posted January 8, 2012 I'll try to have it as soon as possible, what about 1 month or so? Can you describe in detail the reasons why you need it? It will clearly help us when "selling" why exclusive checkout on a DVCS is a differentiation! Link to comment Share on other sites More sharing options...
mdutt Posted February 23, 2012 Report Share Posted February 23, 2012 Hello there, long time since I posted something. I ran into the same issue like the thread starter and wondered if you already were able to implement the announced feature since we have the same issue with binary files and solving it by management is not very suitable - at least for the long run ;-) Looking forward to hear from you. Link to comment Share on other sites More sharing options...
manu Posted February 23, 2012 Report Share Posted February 23, 2012 Aha!! you read our minds! We are currently developing it!! There is one developer on it right now, it will be ready in 1, 2 or 3 weeks maximum. We want to have it for the San Francisco GDC conference. 1 Link to comment Share on other sites More sharing options...
roadrunner Posted March 10, 2012 Author Report Share Posted March 10, 2012 Is exclusive checkout near completion? Link to comment Share on other sites More sharing options...
manu Posted March 12, 2012 Report Share Posted March 12, 2012 Yep! We are using it right now internally Link to comment Share on other sites More sharing options...
andsee Posted March 19, 2012 Report Share Posted March 19, 2012 That's good news, fingers crossed it will be released soon. We are just evaluating plastic at the moment and need to avoid losing work when two people work on a binary file simultaneously, as selecting one or the other as the result of a merge is not acceptable. What are your thoughts on allowing a project to be setup so that certain file extensions or pattern matches can only be checked out exclusively? I would hope that such files also automatically received the make read only option on clients. Our ideal working scenario is that any files as possible work in the plastic way, in that they can be writable all the time on the client and edited by anyone at any time. These files would be any file that can be merged or that carries little risk of loss of work if a merge question of select which one you want is presented. However some binary files need protection and you don't want users changing them accidentally without first ensuring that no one else is working with that file. I can't see a safe way of working with Plastic without this. Link to comment Share on other sites More sharing options...
manu Posted March 20, 2012 Report Share Posted March 20, 2012 Hello andsee, I think the 4.1 with the exclusive checkout feature will be released this week. I'll shortly explain you how it works. The exclusive checkout (locking) can now be configured per path. To configure it create a file "lock.conf" in the server directory with the following format: rep:local_repname lockserver:server:port path_rules where * local_repname: is the name of the repository where you want to perform exclusive checkouts * server: the lock server * port: the port where the lock server is configured * path_rules: an entry per rule specifiying file names with wildcards Example: rep:default lockserver:localhost:8084 *.doc *.xls *.jpg document.vcs /install/readme/* Once the file "lock.conf" has been created and the server restarted, each time a file matching the rules is checkedout, it will be checkedout in exclusive mode (locked), so no other checkout can happen. Link to comment Share on other sites More sharing options...
roadrunner Posted March 20, 2012 Author Report Share Posted March 20, 2012 The lock.conf sounds like a good option - similar to SVN config file with [auto-props] per extension with the addition of setting a particular repo server as the single lock server. Is there a way to manually select a file for locking without editing the lock.conf file? (Using the current server as the default lock server) Link to comment Share on other sites More sharing options...
manu Posted March 20, 2012 Report Share Posted March 20, 2012 Sorry but not in this first implementation. But I'll propose this idea to the team. Link to comment Share on other sites More sharing options...
roadrunner Posted March 20, 2012 Author Report Share Posted March 20, 2012 Thanks - sounds like 98% coverage with the first implementation. Link to comment Share on other sites More sharing options...
manu Posted March 21, 2012 Report Share Posted March 21, 2012 Yep, but soon or later we will need to implement a way to edit the lock.conf file without editing the file manually. Link to comment Share on other sites More sharing options...
Uvaavu Posted March 23, 2012 Report Share Posted March 23, 2012 Excellent, can't wait to get this implemented! One question: If I need to lock files in multiple Repositories do I simply repeat structure once for each Rep in the same lock.conf file?: rep:local_repname1 lockserver:server:port path_rules rep:local_repname2 lockserver:server:port path_rules etc? Link to comment Share on other sites More sharing options...
manu Posted March 23, 2012 Report Share Posted March 23, 2012 Yep! That's the way! Link to comment Share on other sites More sharing options...
psantosl Posted April 11, 2012 Report Share Posted April 11, 2012 If you can't wait, send an email to support and we will send you the current 4.1. The official one will be out as soon as the new website gets ready. 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