Index: svnadmin/hooks/post-commit
===================================================================
--- svnadmin/hooks/post-commit	(revision 362615)
+++ svnadmin/hooks/post-commit	(revision 362616)
@@ -1,68 +1,71 @@
 #!/bin/sh
 
 # $FreeBSD$
 
 # POST-COMMIT HOOK
 #
 # The post-commit hook is invoked after a commit.  Subversion runs
 # this hook by invoking a program (script, executable, binary, etc.)
 # named 'post-commit' (for which this file is a template) with the 
 # following ordered arguments:
 #
 #   [1] REPO         (the path to this repository)
 #   [2] REV          (the number of the revision just committed)
 #
 # The default working directory for the invocation is undefined, so
 # the program should set one explicitly if it cares.
 #
 # Because the commit has already completed and cannot be undone,
 # the exit code of the hook program is ignored.  The hook program
 # can use the 'svnlook' utility to help it examine the
 # newly-committed tree.
 #
 # On a Unix system, the normal procedure is to have 'post-commit'
 # invoke other programs to do the real work, though it may do the
 # work itself too.
 #
 # Note that 'post-commit' must be executable by the user(s) who will
 # invoke it (typically the user httpd runs as), and that user must
 # have filesystem-level permission to access the repository.
 #
 # On a Windows system, you should name the hook program
 # 'post-commit.bat' or 'post-commit.exe',
 # but the basic idea is the same.
 # 
 # The hook program typically does not inherit the environment of
 # its parent process.  For example, a common problem is for the
 # PATH environment variable to not be set to its usual value, so
 # that subprograms fail to launch unless invoked via absolute path.
 # If you're having unexpected problems with a hook program, the
 # culprit may be unusual (or missing) environment variables.
 # 
 # Here is an example hook script, for a Unix /bin/sh interpreter.
 # For more examples and pre-written hooks, see those in
 # the Subversion repository at
 # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
 # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
 
 
 REPO="$1"
 REV="$2"
 
 . /s/svn/ports/hooks/scripts/env.sh
 
 # update conf/ and hooks/.
 update-root.sh "$REPO" "$REV"
 
 # commit mail
 mailer.py commit "$REPO" "$REV" /s/svn/ports/conf/mailer.conf
 
 # mfh
 
 mfh.sh "${REPO}" "${REV}"
 
 # Ping bugzilla if there's a reference
 notify_bz.sh "$REPO" "$REV"
 
 #commit-email.pl "$REPO" "$REV" commit-watchers@example.org
 #log-commit.py --repository "$REPO" --revision "$REV"
+
+TOKEN=`cat /usr/local/etc/jenkins.token | xargs`
+/usr/bin/fetch --no-verify-peer -o /dev/null -q "https://jenkins.freebsd.org/jenkins/job/FreeBSD_ports_ci_head_master/buildWithParameters?token=${TOKEN}&revision=${REV}" || :
Index: svnadmin/hooks/post-revprop-change
===================================================================
--- svnadmin/hooks/post-revprop-change	(revision 362615)
+++ svnadmin/hooks/post-revprop-change	(revision 362616)
@@ -1,64 +1,58 @@
 #!/bin/sh
 
 # $FreeBSD$
 
 # POST-REVPROP-CHANGE HOOK
 #
 # The post-revprop-change hook is invoked after a revision property
 # has been added, modified or deleted.  Subversion runs this hook by
 # invoking a program (script, executable, binary, etc.) named
 # 'post-revprop-change' (for which this file is a template), with the
 # following ordered arguments:
 #
 #   [1] REPOS-PATH   (the path to this repository)
 #   [2] REV          (the revision that was tweaked)
 #   [3] USER         (the username of the person tweaking the property)
 #   [4] PROPNAME     (the property that was changed)
 #   [5] ACTION       (the property was 'A'dded, 'M'odified, or 'D'eleted)
 #
 #   [STDIN] PROPVAL  ** the old property value is passed via STDIN.
 #
 # Because the propchange has already completed and cannot be undone,
 # the exit code of the hook program is ignored.  The hook program
 # can use the 'svnlook' utility to help it examine the
 # new property value.
 #
 # On a Unix system, the normal procedure is to have 'post-revprop-change'
 # invoke other programs to do the real work, though it may do the
 # work itself too.
 #
 # Note that 'post-revprop-change' must be executable by the user(s) who will
 # invoke it (typically the user httpd runs as), and that user must
 # have filesystem-level permission to access the repository.
 #
 # On a Windows system, you should name the hook program
 # 'post-revprop-change.bat' or 'post-revprop-change.exe',
 # but the basic idea is the same.
 # 
 # The hook program typically does not inherit the environment of
 # its parent process.  For example, a common problem is for the
 # PATH environment variable to not be set to its usual value, so
 # that subprograms fail to launch unless invoked via absolute path.
 # If you're having unexpected problems with a hook program, the
 # culprit may be unusual (or missing) environment variables.
 # 
 # Here is an example hook script, for a Unix /bin/sh interpreter.
 # For more examples and pre-written hooks, see those in
 # the Subversion repository at
 # http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
 # http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
 
 
 #REPOS="$1"
-
-REV="$2"
-
+#REV="$2"
 #USER="$3"
 #PROPNAME="$4"
 #ACTION="$5"
 #
 #commit-email.pl --revprop-change "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org
-
-TOKEN=`cat /usr/local/etc/jenkins.token | xargs`
-
-/usr/bin/fetch --no-verify-peer -o /dev/null -q "https://jenkins.freebsd.org/jenkins/job/FreeBSD_ports_ci_head_master/buildWithParameters?token=${TOKEN}&revision=${REV}" || :