Jump to content

Exclusive Checkout with plastic cloud as central node


Recommended Posts

Hi Joel,

In this blog post, we provided a solution for distributed locks but let me explain you why this is not good at all:

- If you follow this workflow, and you checkout an item, then if your coworker tries to checkout the same item, they will have a message alerting that the items is locked by you. So far do good.

- When you checkin your changes, you coworker will be able to checkout the item is his local repo. Them problem is you cannot be sure that your coworker has previouly pulled your branch so they may not be working with the last item version. So technically they will be able to locally lock the item and commit the changes. But as soon as they try to push their changes to the central repo, they will figure out that they were not working with the last version and they will need to resolve a conflict.

NOTE: It's in our roadmap to fully support distributed locks but for now our recommendation is following a centralized workflow if you need to use locks.

Regards,

Carlos.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...