I know about that, it's enabled for both Jobs. The only difference between them is that the second Job is set to a subdirectory inside the repository.
Am Freitag, 6. Mai 2016 14:00:01 UTC+2 schrieb Daniel Beck: > > > On 06.05.2016, at 13:45, frank...@gmail.com <javascript:> wrote: > > > > The only difference is that the second Job is set to a subdirectory > inside the repository and i'd like to keep it that way. Even when i commit > a file inside "subversion/repos/mainframe/subdir" the second Job doesn't > get polled, only the first. > > Both jobs need to have the SCM trigger enabled, possibly without schedule. > Otherwise they ignore post-commit hooks. > > Quoting https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin: > > > Jobs on Jenkins need to be configured with the SCM polling option to > benefit from this behavior. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e1a486af-e3f9-498c-88b0-40419140e8da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
