Would love a post commit hook that "calls" configurable web hook aka HTTP POST to url.

Configurable would be:

URL which allows at least these string replacements $REV, $REPOS. The two arguments to post-commit svn hook.
USER HTTP Basic Auth username
PASS HTTP Basic Auth password

Unfortunately, for a variety of reasons we will not be able to allow custom Subversion hooks per-instance.

For those who are watching this issue or otherwise interested, it would be helpful if you could file new issues describing the specific functionality that you're looking for. There may be alternative implementations that we could support, and we will consider implementing popular hook requests as a user-configurable option across the board (similar to the existing hook to check for an issue key in the commit message).

Thanks,
Tim Moore
Atlassian

What about pre- hooks that can approve/deny actions? In particular, pre-revprop-change defaults to "deny" and is needed to allow Bazaar to manipulate the Author/Date attribute of pushed revisions to match the original author/date.

the list of plans that should be triggered post commit could be listed in the svn commit hook section.

https://support.atlassian.com/browse/BSP-2633

When a plan is configured with 'Repository triggers' as a trigger strategy - would it be possible to insert the <PLAN-KEY> into <SVN-ROOT>/hooks/post-commit ? Not sure if svn needs to be restarted..

See http://confluence.atlassian.com/display/BAMBOO/Triggering+a+Build+on+Code+Check-in

We've decided not to allow this for now, as:

• We don't want to allow shell access for security reasons, and a web UI would be painful to develop and debug scripts in, particularly ones which rely on other files or are not location-independent.
• Scripts running on the server are constrained by what software is installed on the VM. People often want custom Perl modules, for instance, which we cannot install per-instance.
• Allowing arbitrary customer-uploaded commands to run on the server is a security risk and a source of problems (hangs, deadlocks) that we wouldn't have the knowledge to debug, and customers don't have access to debug.
• There is a viable alternative for post-commits which avoids all these problems: create a local mirror of the Studio Subversion, kept in sync with 'svnsync', and add your post-commit hook to the local repository. Eg:

  mkdir studiosvn
  svnadmin create studiosvn
  echo '#!/bin/sh' > studiosvn/hooks/pre-revprop-change
  chmod +x studiosvn/hooks/pre-revprop-change
  svnsync init file://`pwd`/studiosvn http://<account>.jira.com/svn
  svnsync sync file://`pwd`/studiosvn
  

  Then put your post-commit hook in studiosvn/hooks/post-commit

Moving to 1.7