Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was used to having a post-commit hook trigger processing of the commit message by Trac (SVN repository). The comment (or action) was added immediately.

Now I switched to Mercurial as a VCS and Redmine as a ticketing system. Redmine does recognize information in changeset/commit messages like "refs #185" - but it takes several minutes to appear in the ticket.

Any ideas why this is? Is the routine to grab the changesets called periodically somehow?

share|improve this question
up vote 5 down vote accepted

Well, this Redmine feature request gives it away:

Currently, new changeset information is only fetched when you view the repository. So if you update an issue, and mention a revision in it, it doesn't get hyperlinked until someone has viewed the repository.

While I did not find a ready-made post-commit hook to update the Redmine with new changesets, the poor man's solution is cron of course. This questions discusses it: Redmine: fetch changesets from cron job

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.