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

SCM polling broken for servers with variable in path

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • subversion-plugin
    • None

      SCM polling broke for me after updating to: 1.605
      Before this i was running 1.591

      The log shows:
      no revision found corresponding to svn://$SVN_SERVER/path; known: [svn://my.servername.com/path]

      And it simply never triggered any of the builds for that reason. Apparently something changed in how or when the SCM paths get expanded.

      Regardless of the change, isn't the fallback of triggering a build in case of "no revision found corresponding", a safer fallback strategy ?

          [JENKINS-27620] SCM polling broken for servers with variable in path

          Daniel Beck added a comment -

          Did you also update the Subversion Plugin at the same time you updated Jenkins?

          Daniel Beck added a comment - Did you also update the Subversion Plugin at the same time you updated Jenkins?

          Derk-Jan Hartman added a comment -

          This is highly likely yes.

          Derk-Jan Hartman added a comment - This is highly likely yes.

          Daniel Beck added a comment -

          Should be trivial to determine based on the file modification date of JENKINS_HOME/plugins/subversion.hpi (or .jpi).

          Both current and previous Subversion plugin versions would be helpful.

          Also, anything interesting in the logs.

          Daniel Beck added a comment - Should be trivial to determine based on the file modification date of JENKINS_HOME/plugins/subversion.hpi (or .jpi). Both current and previous Subversion plugin versions would be helpful. Also, anything interesting in the logs.

          Derk-Jan Hartman added a comment -

          Actually, now that i'm looking a bit further, it seem that the real problem is that SCM polling isn't able to find the credentials anymore. This information is in the SCM polling log, and not in the Jenkins master log.

          Manually triggering the build, SVN has no problem finding the credentials.

          Derk-Jan Hartman added a comment - Actually, now that i'm looking a bit further, it seem that the real problem is that SCM polling isn't able to find the credentials anymore. This information is in the SCM polling log, and not in the Jenkins master log. Manually triggering the build, SVN has no problem finding the credentials.

          Derk-Jan Hartman added a comment -

          My issue seems duplicate with JENKINS-22542
          Downgrading to 2.4.5 indeed made polling work again.

          Derk-Jan Hartman added a comment - My issue seems duplicate with JENKINS-22542 Downgrading to 2.4.5 indeed made polling work again.

          Daniel Beck added a comment -

          Resolving as duplicate then.

          Daniel Beck added a comment - Resolving as duplicate then.

            Unassigned Unassigned
            thedj Derk-Jan Hartman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: