Changes committed to the SVN repo don't get detected by Bamboo branches

Here are the steps to reproduce the misbehavior:

• Add a branch plan based on an SVN branch
• Configure that repository triggers the build
• Commit a change to that repository branch and see that the branch gets queued up
• By the time the previous build is running, commit another change. It's supposed to trigger the build again, and the build should get queued up. Every next commit should be queued up, but Bamboo doesn't detect the changes:

  2013-09-30 09:38:19,731 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-1] [DashboardCachingManagerImpl] Plan cache updated for 1 plans in 0:00:00.076
  2013-09-30 09:38:19,732 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-13] [DependencyChainListener] Checking children plans of [PROJ1-SVNT0] for plan PROJ1-SVNT0-8
  2013-09-30 09:38:19,734 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-13] [DependencyChainListener] Finished checking children plans of 'Project-1 - SVNTest - epicenter-2.0-branch' for plan PROJ1-SVNT0-8
  2013-09-30 09:38:21,714 INFO [qtp901833818-567] [AccessLogFilter] 127.0.0.1 GET http://localhost:8085/bamboo/api/rest/updateAndBuild.action?buildKey=PROJ1-SVNT 179739kb
  2013-09-30 09:38:21,741 INFO [4-BAM::PlanExec:pool-7-thread-4] [SvnRepository] Collecting changes for 'PROJ1-SVNT0' on path 'file:///Users/akhachatryan/dev/Repositories/SVNCustomer/SVNTest/branches/epicenter-2.0-branch' from version 6338 to -1
  2013-09-30 09:38:21,741 INFO [4-BAM::PlanExec:pool-7-thread-1] [SvnRepository] Collecting changes for 'PROJ1-SVNT2' on path 'file:///Users/akhachatryan/dev/Repositories/SVNCustomer/SVNTest/branches/epicenter-1.3-new-ui' from version 6338 to -1
  2013-09-30 09:38:21,741 INFO [4-BAM::PlanExec:pool-7-thread-2] [SvnRepository] Collecting changes for 'PROJ1-SVNT1' on path 'file:///Users/akhachatryan/dev/Repositories/SVNCustomer/SVNTest/branches/epicenter-2.1-branch' from version 6338 to -1
  2013-09-30 09:38:21,746 INFO [4-BAM::PlanExec:pool-7-thread-1] [ChangeDetectionListenerAction] No changes found for 'PROJ1-SVNT2'
  2013-09-30 09:38:21,746 INFO [4-BAM::PlanExec:pool-7-thread-2] [ChangeDetectionListenerAction] No changes found for 'PROJ1-SVNT1'
  2013-09-30 09:38:21,746 INFO [4-BAM::PlanExec:pool-7-thread-4] [ChangeDetectionListenerAction] No changes found for 'PROJ1-SVNT0'
  

  For the trunk, it doesn't update the build queue immediately, but after some time the builds appear.

This is the configuration in the post-commit SVN hook:

/Users/akhachatryan/Atlassian/Bamboo4.4.5/atlassian-bamboo-4.4.5/scripts/svn-triggers/postCommitBuildTrigger.sh http://localhost:8085/bamboo PROJ1-SVNT

This is the content of the postcommitBuildTrigger file:

#!/bin/bash

# the base url of the bamboo server
#baseurl="$1/updateAndBuild.action?buildKey="
baseurl="$1/api/rest/updateAndBuild.action?buildKey="

#
# Use the REST API to trigger a build
#

# Moves to the 2nd param (first is URL)
shift
# Loop for each build key
while (( "$#" )); do

   #
   # Invoke the trigger
   #
   remoteCall=$baseurl$1
   echo "Detected last directory that was committed ... triggering $remoteCall"
   /usr/local/bin/wget --timeout=10 -t1 $remoteCall -O /dev/null

   shift
done


exit 0