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

Build is not trigger by SCM trigger on a SVN project that has svn-external properties

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: All

      I have a project that has a directory that has a svn-externals property on it.
      The project structure is:

      trunk-+--module(dir)

      +--main.cpp

      The module directory has svn-externals property:
      CBSVN https://optimusprime:8443/svn/svn_playground/CBTortoiseSVN/trunk
      It is stable at revision 1

      The trunk has URL:
      https://optimusprime:8443/svn/svn_playground/sleep/trunk

      Hudson monitors the trunk URL and sees the module directory with svn-externals
      property correctly however it sees no changes in the trunk.

      scmPollLog says:
      Started on 3-mrt-2009 23:23:17
      https://optimusprime:8443/svn/svn_playground/CBTortoiseSVN/trunk heeft revisie 1
      Done. Took 0,2 seconden
      No changes

      Note that the trunk is not mentioned in scmPollLog

      However the trunk has changed(main.cpp) but the build is not triggered. If I
      trigger build by hand hudson reports indeed changes in the trunk:

      Revisions

      Is it a bug? Can I tweak hudson in such a way that it works with subversion
      svn-externals property

            Unassigned Unassigned
            jan_van_den_borst jan_van_den_borst
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: