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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      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.

            Assignee:
            Kohsuke Kawaguchi
            Reporter:
            Matthew Webber
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: