Post-Commit Hook to trigger automatic Jenkins Build

Question

I know that there are many similar postings, but I have not found a solution, and the advice and solutions presented in the other posts don\'t quite jive with what I\'m seei

Answer 1

The article you linked says

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.

and

For this to work, your Jenkins has to allow anonymous read access (specifically, "Job > Read" access) to the system. If access control to your Jenkins is more restrictive, you may need to specify the username and password, depending on how your authentication is configured.

Does you server meets this restrictions?