Clarifications using Subversion

[Vijay Peddamallu <vi...@ajg.com>]

Dear All,
We are working on enhancing our repository and put some controls hence. In this regard, seek clarifications on the following. Please note that we are on Subversion v 1.7 as I write.

1.       Is there any way that we can restrict "svn delete" command to limited set of users? While we understand that there is a way to recover the deleted version, would still like to understand if this is an option in first place.

2.       If I lock source code on my name, can we apply a restriction that only I can unlock it. Otherwise, admin?

Thanks,
Vijay Pedamallu
Tech Lead, Global Oracle HRIS
Corporate Human Resources
[cid:image001.png@01CFDC05.02039490]
Arthur J. Gallagher & Co.
M: +91-98858-04770
www.ajg.com<http://www.ajg.com/>   |  Vijay_Peddamallu@ajg.com<ma...@ajg.com>

Confidentiality Note:  This e-mail and any files transmitted with it are intended only for the person or entity to which it is addressed and may contain confidential material and/or material protected by law.  Any retransmission or use of this information may be a violation of that law.  If you received this in error, please contact the sender and delete the material from any computer.

[cid:image002.jpg@01CFDC05.02039490]

Re: Clarifications using Subversion

[Andreas Stieger <An...@gmx.de>]

Hi,
 
Vijay Peddamallu wrote:
> can restrict “svn delete” command to limited set of users?

Pre-commit hook that examines the pending transactions and rejects accordingly.
http://svnbook.red-bean.com/en/1.7/svn.ref.reposhooks.pre-commit.html

> If I lock source code on my name, can we apply a restriction that only I can unlock it. Otherwise, admin?
 
Pre-unlock hook that examines the unlock request and restricts as required.
http://svnbook.red-bean.com/en/1.7/svn.ref.reposhooks.pre-unlock.html 

Note that svn's locking feature is not a write protection, but intended for serializing edits to files where individual changes cannot be merged - such as binary assets, images.

For that and the above, I have found that project policies work much better than technical restrictions you are asking for. Certainly in reasonably motivated professional environments.

Andreas

Re: Clarifications using Subversion

[Eric Johnson <er...@tibco.com>]

While the other response gives you the clues to (mostly) enforce what 
you want, I strongly encourage you to consider how to avoid using 
tooling to solve what is probably really a management problem.

The more you customize your hooks, the more difficult it might be to 
move your Subversion installation to a new environment, a cloud 
provider, or a commercial offering, just for example.

Hooks are best applied to business rules that are not about people.

You can use them the way you're asking, but long term, you might not 
want to.

Eric.

On 4/11/16 6:32 AM, Vijay Peddamallu wrote:
>
> Dear All,
>
> We are working on enhancing our repository and put some controls 
> hence. In this regard, seek clarifications on the following. Please 
> note that we are on Subversion v 1.7 as I write.
>
> 1.Is there any way that we can restrict “svn delete” command to 
> limited set of users? While we understand that there is a way to 
> recover the deleted version, would still like to understand if this is 
> an option in first place.
>
> 2.If I lock source code on my name, can we apply a restriction that 
> only I can unlock it. Otherwise, admin?
>
> *Thanks,*
>
> *Vijay Pedamallu*
>
> Tech Lead, Global Oracle HRIS
>
> Corporate Human Resources
> cid:image001.png@01CFDC05.02039490
> Arthur J. Gallagher & Co.
>
> M: +91-98858-04770
>
> www.ajg.com <http://www.ajg.com/>   | Vijay_Peddamallu@ajg.com 
> <ma...@ajg.com>
>
> *Confidentiality Note:* This e-mail and any files transmitted with it 
> are intended only for the person or entity to which it is addressed 
> and may contain confidential material and/or material protected by 
> law.  Any retransmission or use of this information may be a violation 
> of that law.  If you received this in error, please contact the sender 
> and delete the material from any computer.
>
> cid:image002.jpg@01CFDC05.02039490
>