Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53839

Builds triggered when there is no change (Subversion polling)

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.138.1 Docker, Subversion plugin 2.12.1, SCM API 2.2.7
    • Similar Issues:

      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/<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
      

       

       

        Attachments

          Issue Links

            Activity

            Hide
            kerrhome Shannon Kerr added a comment -

            btw, I've disabled lightweight checkout for now.  Will Jenkins keep trying to build if there are no changes but the last build failed?  I want to say that I've noticed it doing that at times, but I've not looked closely.

            Show
            kerrhome Shannon Kerr added a comment - btw, I've disabled lightweight checkout for now.  Will Jenkins keep trying to build if there are no changes but the last build failed?  I want to say that I've noticed it doing that at times, but I've not looked closely.
            Hide
            kerrhome Shannon Kerr added a comment - - edited

            I said above "Before moving to the newest Subversion plugin and lightweight checkouts for the Jenkinsfile, we did not have builds that triggered in error", but that is not exactly true.  We were not having builds triggered in error for a long time, but there was a time a month or so ago where we were seeing builds triggered and the change list showed no changes were made.  We've not seen that for a while though.  Things have been doing well up until the latest plugin change.  I noted this issue here: https://issues.jenkins-ci.org/browse/JENKINS-17614?focusedCommentId=343869&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-343869

            After a weekend of little to no SVN activity, the builds have stopped triggering at least (with lightweight checkout disabled).

            Show
            kerrhome Shannon Kerr added a comment - - edited I said above "Before moving to the newest Subversion plugin and lightweight checkouts for the Jenkinsfile, we did not have builds that triggered in error", but that is not exactly true.  We were not having builds triggered in error for a long time, but there was a time a month or so ago where we were seeing builds triggered and the change list showed no changes were made.  We've not seen that for a while though.  Things have been doing well up until the latest plugin change.  I noted this issue here:  https://issues.jenkins-ci.org/browse/JENKINS-17614?focusedCommentId=343869&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-343869 After a weekend of little to no SVN activity, the builds have stopped triggering at least (with lightweight checkout disabled).
            Hide
            ifernandezcalvo Ivan Fernandez Calvo added a comment -

            I do not think that https://issues.jenkins-ci.org/browse/JENKINS-17614 is related it is a really old issue on a really old version of Jenkins.

            Show
            ifernandezcalvo Ivan Fernandez Calvo added a comment - I do not think that https://issues.jenkins-ci.org/browse/JENKINS-17614 is related it is a really old issue on a really old version of Jenkins.

              People

              • Assignee:
                Unassigned
                Reporter:
                kerrhome Shannon Kerr
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: