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

Editing a projct configuration corrupts the "Local module directory" setting for subversion repositories


    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • subversion-plugin
    • None

      There is a bug when you edit a project configuration that uses Subversion for your Source Code Management

      It is legal and valid for the "Local module directory (optional)" field to be left empty. However, if you edit any part of the configuration at all, and save it, then Hudson now puts "." (without the quotes) in place of the previously empty value for "Local module directory". This is simply incorrect, since "." means something different from "".

      I noticed this problem immediately after upgrading to Hudson 1.382, and I suspcet it was introduced in that version, although it could have been there earlier.

            kohsuke Kohsuke Kawaguchi
            mwebber Matthew Webber
            0 Vote for this issue
            0 Start watching this issue