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

Access problem to SVN server is handled as scm change, but restoring connection is not

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • subversion-plugin
    • None
    • Ubuntu 10.4 (LTS) (64bit)

      We have projects that are triggered by SCM changes. We've noticed that if there is a network failure or server maintenance (connection to SVN server can't be made), situation is handled as SVN change and project is triggered and of course failed.

      When SVN server is back on-line, projects are not triggered automatically, since technically, there is no changes. This results all SCM-triggered projects show as failed until they are triggered manually -or new commits are made.

          [JENKINS-9147] Access problem to SVN server is handled as scm change, but restoring connection is not

          There are no comments yet on this issue.

            Unassigned Unassigned
            swiksted Samu Wikstedt
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: