Peter Romba commented on Bug JENKINS-9529

Complete Jenkins newbie here. I am not using BlameSubversion, but I ran into this same issue--any time I made a commit and SVN fired off the post-commit, I'd see the above error in my Jenkins log.

After scratching my head for a good hour, I noticed a block of text in the Post Commit Hook Section:

Jobs on Jenkins need to be configured with the SCM polling option to benefit from this behavior. This is so that you can have some jobs that are never triggered by the post-commit hook (in the $REPOSITORY/hooks directory), such as release related tasks, by omitting the SCM polling option.
The configured polling can have any schedule (probably infrequent like monthly or yearly). The net effect is as if polling happens out of their usual cycles.

As a test, I set my job to poll SCM on a yearly basis, then I tried my post-commit hook, and it worked.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to