-
Bug
-
Resolution: Not A Defect
-
Major
-
Jenkins version 1.638, Subversion-plugin version 2.5.4
We have an SVN repository with a number of projects and a shared directory that looks something like:
/product/trunk/projects/project1
/product/trunk/projects/project2
/product/trunk/shared
In jenkins we have set up a job to build each separate project. Each of these checks out its project and the shared folder from SVN -so for project1 we check out:
/product/trunk/projects/project1
/product/trunk/shared
Because the shared directory will change frequently, in ways that may not relate to any given project, we have set an excluded region so that we don't build all projects all the time:
/product/trunk/shared/.*
If a change is only made to files in the shared folder, project1 will not build and the SVN polling log will show that the change has been ignored.
If a change is made only to project2, project1 will not build and the SVN polling log will show that there are no changes.
However, if a change is made to project2 and the shared folder, project 1 will be built and the SVN polling log will report that the version of the shared folder has changed.
This is causing us problems as it means we cannot exclude the shared folder from each project and every project builds for all check ins even when there are no related changes.