Jenkins 2.138.1 Docker, Subversion plugin 2.12.1, SCM API 2.2.7
We have several product pipeline builds set to run nightly if there are changes on trunk that meet their include/exclude regions criteria. These are individual, not multibranch, pipeline builds.
We are using lightweight checkouts for the Jenkinsfile, which is located in our repository at
so we list it as Jenkins/<product>/Jenkinsfile in the project configuration (for Script path).
Before moving to the newest Subversion plugin and lightweight checkouts for the Jenkinsfile, we did not have builds that triggered in error. I think that, with lightweight checkouts, the include/exclude region rules are being ignored, but I'm not sure. What I see on the build page is that it thought there were changes, but none of the changes match: