0

Can I control who can commit the projects? I Need to introduce a rule that only one person can commit one specific project at the same time. And the person who want to make changes he only can when he Update the project, that was previously committed.

As in the following example:

    • User 1 working on the project
    • User 2 attempts to commit, but access is denied because User 1 is working on it.
    • User 1 commits the project.
    • User 2 tries to commit to the project and is again rejected.
    • User 2 does Project Update and then commits your changes successfully.

Regards JR

Improve this question
3
  • You want to controll it as root, or give the option that users can handle it individually? Commented Aug 20, 2013 at 17:04
  • I want to control it as a root, i know it is possible but i can't figure out. Commented Aug 20, 2013 at 17:44
  • "I Need to introduce a rule that only one person can commit..." - 1. you don't need this rule 2. You can have nothing more than manual Lock|Unlock Commented Aug 21, 2013 at 9:50

2 Answers 2

Reset to default
1

In tortoise svn you have the posibillty of let the user lock a project, so its almost the behavior you want. The only difference, a user is able to say "I know what I'm doing, and i want to acces anyway" but excepting this, locking an repo, gives you that behavior ;)

E: in tortoisesvn 1.8 simply rightclick the project tortoisesvn->Get Lock/Release Lock

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

I don´t want to Lock the project, i just want a automatically recourse. Thanks for the info but i need is a pre-commit and post-commit rules.
So what is the difference? As i asked you allready before, do you want to force the user to play after this rules? Or is it what you'r talking about slightly different? the explain it plz more specific because your example would be solved by a lock/unlock
I want to force the user to dont commit will the project is open by another user. I dont want users to lock and unlock projects, i want a another way to do this whitout users interact with Tortoise or other svn application
0

There are two ways to do this:

The Path based authorization is built into Subversion and can control, read (checkout only), read-write (commit), or no-access (no checkout). The pre-commit hook can't control read authorization, but is more flexible in setting commit (read-write) authorization.

Improve this answer

7 Comments

With Path Based Authetication is possible to do that? I'm not sure... In Path Based Authetication you can only deny or allow respositories access to the users.
@JorgeRocha See Path based authentication in the Subversion on line manual
Ok you can allow or deny file access to users, but this don't resolve my problem. I want to control the svn user commits.
@JorgeRocha use pre-commit hook to control user commits.
@JorgeRocha The path based authorization allows you to do this. The various permissions are: w allows commits. r allow checkout, but not commit, and null which completely removes access. However, you can use my pre-commit hook if you prefer.
|

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.