Re: new folder

[Campbell Allan <ca...@sword-ciboodle.com>]

On Monday 23 January 2012, sureshkumar nandakumar wrote:
> Hi,
> 
> I would like to restrict new folder creation under in /branches.
> Currently we are using SVN perm files for restrict the read/write
> access control.
> We have around 1000 SVN users, we are in position to control the access
> level.
> 
> Without our knowledge no one should not add any new folders under in
> /branches directory.
> Can anyone suggest me, how can i do this and how to get alert, if any
> new folder is created

I suppose this is tricky if you disregard other options of control. To be 
honest, it isn't clear what you require from your message. Whether it's a 
social solution you want to use and only get notification when a commit to the 
branches directory occurs or if you want to prevent commits. The former I'd 
use a simple post-commit email notification script. 

To prevent commits I'd implement a pre-commit hook that restricts commits to 
the branches directory unless the user and path are in a configuration file. 
I'd go a bit further and add time based control to this too so that the window 
for committing is limited. I'd place the configuration file in a separate 
repository whose access you can completely control and have a post commit 
script to export the file on the server. This allows for an audit and history 
trail to be made.

-- 

Sword Ciboodle
www.sword-ciboodle.com

t +44 141 533 4000

www.sword-group.com
__________________________________________________________________________________
Sword Ciboodle is the trading name of ciboodle Limited (a company 
registered in Scotland with registered number SC143434 and whose 
registered office is at India of Inchinnan, Renfrewshire, UK, 
PA4 9LH) which is part of the Sword Group of companies.

This email (and any attachments) is intended for the named
recipient(s) and is private and confidential. If it is not for you, 
please inform us and then delete it. If you are not the intended 
recipient(s), the use, disclosure, copying or distribution of any 
information contained within this email is prohibited. Messages to 
and from us may be monitored. If the content is not about the 
business of the Sword Group then the message is neither from nor 
sanctioned by us.

Internet communications are not secure. You should scan this
message and any attachments for viruses. Under no circumstances
do we accept liability for any loss or damage which may result from
your receipt of this email or any attachment.
__________________________________________________________________________________

Re: new folder

[Alan Barrett <ap...@cequrux.com>]

On Wed, 01 Feb 2012, sureshkumar nandakumar wrote:
>I want to prevent commits in /branches alone.
>Apart from admin, no one shouldn't add any new folders under in
>/branches folder.
>
>Already We are using svnperm for access control. Can u guide me, how I
>can do this?

svnperms.py can already do this, and the examples in 
svnperms.conf.example are very close to your use case.  
See "example1" in 
<https://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/svnperms.conf.example>, 
where it says that only members of group3 can create tags, and 
adapt it so that only members of your admin group can create 
branches.

--apb (Alan Barrett)

Re: new folder

[sureshkumar nandakumar <su...@gmail.com>]

Hi Allan,

I want to prevent commits in /branches alone.
Apart from admin, no one shouldn't add any new folders under in
/branches folder.

Already We are using svnperm for access control. Can u guide me, how I
can do this?
If possible share your pre-commit script and guide me how i can modify
the script, based on my requirement.


On 2/1/12, Campbell Allan <ca...@sword-ciboodle.com> wrote:
>
> On Monday 23 January 2012, sureshkumar nandakumar wrote:
>> Hi,
>>
>> I would like to restrict new folder creation under in /branches.
>> Currently we are using SVN perm files for restrict the read/write
>> access control.
>> We have around 1000 SVN users, we are in position to control the access
>> level.
>>
>> Without our knowledge no one should not add any new folders under in
>> /branches directory.
>> Can anyone suggest me, how can i do this and how to get alert, if any
>> new folder is created
>
> I suppose this is tricky if you disregard other options of control. To be
> honest, it isn't clear what you require from your message. Whether it's a
> social solution you want to use and only get notification when a commit to
> the
> branches directory occurs or if you want to prevent commits. The former I'd
> use a simple post-commit email notification script.
>
> To prevent commits I'd implement a pre-commit hook that restricts commits to
> the branches directory unless the user and path are in a configuration file.
> I'd go a bit further and add time based control to this too so that the
> window
> for committing is limited. I'd place the configuration file in a separate
> repository whose access you can completely control and have a post commit
> script to export the file on the server. This allows for an audit and
> history
> trail to be made.
>
> --
>
> Sword Ciboodle
> www.sword-ciboodle.com
>
> t +44 141 533 4000
>
> www.sword-group.com
> __________________________________________________________________________________
> Sword Ciboodle is the trading name of ciboodle Limited (a company
> registered in Scotland with registered number SC143434 and whose
> registered office is at India of Inchinnan, Renfrewshire, UK,
> PA4 9LH) which is part of the Sword Group of companies.
>
> This email (and any attachments) is intended for the named
> recipient(s) and is private and confidential. If it is not for you,
> please inform us and then delete it. If you are not the intended
> recipient(s), the use, disclosure, copying or distribution of any
> information contained within this email is prohibited. Messages to
> and from us may be monitored. If the content is not about the
> business of the Sword Group then the message is neither from nor
> sanctioned by us.
>
> Internet communications are not secure. You should scan this
> message and any attachments for viruses. Under no circumstances
> do we accept liability for any loss or damage which may result from
> your receipt of this email or any attachment.
> __________________________________________________________________________________
>
>