bloodhound-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Jouffrey <eric.jouff...@asygn.com>
Subject Reload product configuration
Date Mon, 27 Jan 2014 15:44:58 GMT
Hello everyone,

We are evaluating to use bloodhound as bugtracker for a very small team 
of developers. So far everything seems good for us and it's already a 
quite usable system, meeting what we were looked for. But on our little 
test sever, we face something a bit strange.
[ Configuration is bloodhound 0.8-dev over Apache, SQLite, one active 
project and one SVN repository. SVN repository is mirrored using svnsync. ]

After a new changeset is added, bloodhound seems to randomly be aware it.
For example sometimes page of changeset indicate invalid number, 
sometimes it's good and changeset is displayed
I know that changeset have been correctly added because comments are 
added to tickets that the changeset comment refer to, tickets states 
change if comment contain good syntax, etc.
And after :
- a restart of apache server
  or
- a kill of bloodhound process
or
- a modification of configuration (enable/disable log for exemple)
everything is back to normal


So I have three questions that maybe you can help :
- Is this a bug or something I do wrong into this process, specially 
around svnsync ?
- Is it more a trac or bloodhound related problem ?
- Is there a command for reload configuration that I can execute in the 
hook ?

For now, I'm going to kill the bloodhound process after added changset 
in my post-hook script. But that's ugly.
Thanks by advance if you have any clue.





----------------------------------------------
LOG Extract when changeset cannot be found :
2014-01-23 12:35:26,738 Trac[main] DEBUG: Dispatching 
<ProductRequestWithSession "GET '/changeset/668/MyRepo'">
2014-01-23 12:35:26,740 Trac[session] DEBUG: Retrieving session for ID 
u'user'
2014-01-23 12:35:26,741 Trac[main] DEBUG: Negotiated locale: None -> fr
2014-01-23 12:35:26,747 Trac[api] WARNING: Unable to find repository 
'(default)' for synchronization
2014-01-23 12:35:26,750 Trac[chrome] DEBUG: Prepare chrome data for request
2014-01-23 12:35:26,774 Trac[web_ui] DEBUG: {'active': False, 'name': 
'wiki', 'label': <Element "a">}
2014-01-23 12:35:26,774 Trac[web_ui] DEBUG: {'active': True, 'name': 
'browser', 'label': <Element "a">}
2014-01-23 12:35:26,774 Trac[web_ui] DEBUG: {'active': False, 'name': 
'tickets', 'label': <Element "a">}
2014-01-23 12:35:26,774 Trac[main] WARNING: [172.16.128.112] 
HTTPNotFound: 404 Numéro de révision non valide (Aucune révision 668 
dans ce dépôt)
2014-01-23 12:35:26,880 Trac[main] DEBUG: Dispatching 
<ProductRequestWithSession "GET 
'/chrome/dashboard/css/bootstrap-responsive.css'">
----------------------------------------------
My post-revprop-change hook :
REPOS="$1"
REV="$2"
USER="$3"
PROPNAME="$4"
ACTION="$5"

#/bin/echo "`date` post-revprop $REPOS $REV $USER $PROPNAME $ACTION" >> 
/root/svnsync.log # Log all actions

if [ "$PROPNAME" = "svn:sync-last-merged-rev" ]; then
     YOUNGEST_REV=`svnlook youngest /opt/svn/myRepo`

     # Start virtualeven for bloodhound
     source /opt/bloodhound/installer/bloodhound/bin/activate
     # Fire update to Bloodhound
     trac-admin /opt/bloodhound/installer/bloodhound/environments/main/ 
changeset added "myRepo" $YOUNGEST_REV

     # Restart bloodhound daemon by killing it..
     PID=`pgrep -U bloodhound`
     #echo "Kill the bloodhound daemon, PID $PID"
     if [[ ! -z $PID ]]
     then
         kill $PID
     fi

fi


Mime
View raw message