On Tuesday, October 14, 2014 9:38:12 AM UTC-7, Oscar Edvardsson wrote: > > Hi, > > I'm actually using Bloodhound at the moment, but I believe this is an > issue that I have had and have with Trac. > > When pushing changes to our centralized Mercurial repo where > Bloodhound/Trac is hosted, I would like to use the Fix #99 to automatically > mark the issue as fixed. This does not happen though. I believe this is a > configuration/permission error, but I can not find the source or a way to > debug it. > > *Setup* > Environment in /bloodhound/. > Repo in /repo/repo1. > Post-commit hooks in /bloodhound/plugins/hooks.py > > repo1/.hg/hgrc looks like follows: > > [web] > allow_push = * > push_ssl = false > > [hooks] > commit = python:/bloodhound/plugins/hooks.py:add_changesets > changegroup = python:/bloodhound/plugins/hooks.py:add_changesets > > [trac] > env = /bloodhound/ > trac-admin = > /usr/local/apache-bloodhound-0.7/installer/bloodhound/bin/trac-admin > > I have also verified that [trac] repository_sync_per_request is set to > empty in trac.ini. > > *What works* > I can run the command from trac-admin to successfully sync the repository > and marking the issue as fixed (once I've pushed). > I followed the last answer in this > <http://stackoverflow.com/questions/9589955/easy-painless-way-to-test-new-mercurial-hooks-that-are-works-in-progress> > thread > and was able to run the Python script using SSH, which is successful (i.e. > returns false and issues are marked as resolved). > > *What doesn't work* > However, when I push the issues are not marked as resolved, even though I > can see the changesets in Trac. > There are no messages in trac.log. > > How can I debug this further? I guess what I would like to know is if the > hook is ever run, but how would I do that? (Don't know how to write/modify > Mercurial hooks) If it is run, I would like to output the results to try to > find the source of the error. > > Any help would be appreciated, this has been bugging me for quite some > time now. > > Regards >
You say that the ticket is not closed. Is the changeset message inserted into the ticket? It does sound like a permissions issue. What version of Trac are you running? Some issues were resolved in 1.0.1 with case-sensitive authnames and the post-commit hook. The user pushing the changes will need to have TICKET_MODIFY. Try setting: [trac] commit_ticket_update_check_perms = false <https://lh5.googleusercontent.com/-Tyi2OMNHSgg/VGfHCdD8riI/AAAAAAAAB44/kMqFE4AX8Ts/s1600/TicketSection.png> -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
