jenkinsci / jenkinsci/subversion-plugin

[JENKINS-53839] Builds triggered when there is no change (Subversion polling)

Open
#1,488 4 comments 0 reactions 0 assignees View on GitHub
component:subversion-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

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

svn://url/trunk/Jenkins//Jenkinsfile

so we list it as Jenkins//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:

 

 

Polling Log

 
View as plain text
This page captures the polling log that triggered this build.
 
Started on Sep 28, 2018 12:51:02 AM
no polling baseline in /var/jenkins_home/jobs/Big Product Trunk/workspace@​libs/company on
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘//svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Using sole credentials builder/****** (SVN access) in realm ‘//svnUrl:3690> CompanyName REPO SVN Repository’
  (changed from 243,568)
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘//svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘//svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘//svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Done. Took 61 ms
Changes found

 

 

---
Originally reported by kerrhome, imported from: Builds triggered when there is no change (Subversion polling)


  • status: Open
  • priority: Major
  • component(s): subversion-plugin
  • resolution: Unresolved
  • votes: 2
  • watchers: 6
  • imported: 20251212-090250

Raw content of original issue

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



svn://url/trunk/Jenkins/<product>/Jenkinsfile


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:

 

 



Polling Log

 
View as plain text
This page captures the polling log that triggered this build.
 
Started on Sep 28, 2018 12:51:02 AM
no polling baseline in /var/jenkins_home/jobs/Big Product Trunk/workspace@libs/company on
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘<svn://svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Using sole credentials builder/****** (SVN access) in realm ‘<svn://svnUrl:3690> CompanyName REPO SVN Repository’
  (changed from 243,568)
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘<svn://svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘<svn://svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Received SCM poll call on master for Big Product Trunk on Sep 28, 2018 12:51:02 AM
Using sole credentials builder/****** (SVN access) in realm ‘<svn://svnUrl:3690> CompanyName REPO SVN Repository’
svn://svnUrl/REPO/trunk is at revision 243,728
Done. Took 61 ms
Changes found


 

 

  • environment: Jenkins 2.138.1 Docker, Subversion plugin 2.12.1, SCM API 2.2.7

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.