Job pointing to svn subdirectory not being polled

10 views
Skip to first unread message

frank...@gmail.com

unread,
May 6, 2016, 7:45:05 AM5/6/16
to Jenkins Users
I have two Jobs in Jenkins, one which has a working copy of "subversion/repos/mainframe" and another that has a working copy of "subversion/repos/mainframe/subdir".

I then created a hook on the mainframe repository to call Jenkins on any commit. This hook has been triggering my first Job without a Problem. But the second Job doesn't get triggered at all. 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.

How can i get the second Job to Trigger on commits?

Daniel Beck

unread,
May 6, 2016, 8:00:01 AM5/6/16
to jenkins...@googlegroups.com

> On 06.05.2016, at 13:45, frank...@gmail.com 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.

frank...@gmail.com

unread,
May 6, 2016, 8:12:39 AM5/6/16
to Jenkins Users, m...@beckweb.net
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.
Reply all
Reply to author
Forward
0 new messages