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

Subversion exclusions not preventing a build triggered by scm change

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None

      (jenkins 1.472, subversion plugin 1.42, on windows os)
      I have a build job that polls the svn repository for changes and builds if any are found. In the svn configuration, I have set up an exclusion for our version file (which is updated right before committing the build changes). You can see from the output below that the exclusion was recognized but the build was triggered anyway.
      ------------------------------------
      Started on Sep 12, 2012 3:01:53 AM
      Received SCM poll call on slave_a builder for project_a on Sep 12, 2012 3:01:54 AM
      http://foo/bar/project_a is at revision 4,191
      Ignored revision 4,191: Found only excluded paths: /foo/bar/project_a/version.txt
      (changed from 3,962)
      Done. Took 1.9 sec
      Changes found

          [JENKINS-15141] Subversion exclusions not preventing a build triggered by scm change

          There are no comments yet on this issue.

            Unassigned Unassigned
            javamllama Maddy Goss
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: