Questions regarding deny push & repo creation for customers

[Mcadams, Philip W]

Hello,

I have a couple of problems that we are trying to solve internally and seeking help from the wider Mercurial community:


1)      Disallow pushing to a repository: Currently our team is trying to solve a problem of locking down our main repository once someone pushes bad code to allow engineers to fix the repository.  The original process used was to send an email to all engineers stating to "not push" until informed that they could.  As you could guess that process has not been successful.  Currently we are working on a hook to manage the allow/deny push and in the meantime we are simply removing the write permissions directly on the repository (we are on windows).  We've found documentation on modifying the .hgrc file's "allow_push" parameter and are still testing it.  My question is if there an official method recommended by Mercurial to solve this problem?  Is changing the "allow_push" parameter it? Ideally we would like the customer to have control of the lock/unlock and are considering creating a script that would allow the customer to update the hgrc file directly through their script.  Before continuing to hack at this I thought I'd ask is if there way to solve this problem that we are not considering.

2)      Automating Repo Creation: Currently there is a request for customers to be able to create their own Mercurial repositories.  Our current process involves the Mercurial systems administrator manually creating repository's directly on the Mercurial server.  We are working on creating a Web interface that would allow a customer to create a repo and apply the appropriate permissions.  My question here is if there is a way to do this through the hgweb directly or through a third party tool that I'm not aware of?

Thank you.

Philip McAdams
Software Configuration Management Engineer
NSG ISE Test Engineering & SCM
Desk: (916) 377-6156 Cell: (678) 770-3176 Pole: FM3-1-D7

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20150109/128d9576/attachment.html>