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

Wrong charset entry in build.xml after hudson-Upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • core
    • None
    • Ubuntu 8.04.3
      Glassfish v3 -> Hudson 1.345-1.346
      cvsnt
      Linux filesystem: UTF-8
      Environment: LANG=de_DE.UTF-8

      Until Hudson 1.343 I had no problem processing files with cvs und german umlauts. After cvs-update all changes are computet correctly.

      Starting with Hudson 1.345 (and 1.346) all builds with files including german umlauts (e.g. รค) breaks while computing the cvs-changes. (something like command has NULL value).

      Searching for the reason I detected that the build.xml-files in the hudoson-job-build-subdirectories had until Hudson 1.343 the charset entry UTF-8, and AFTER Hudson 1.345 (also 1.346) the entry US-ASCII.

          [JENKINS-5650] Wrong charset entry in build.xml after hudson-Upgrade

          dschettl added a comment -

          Is solved with Hudson 1.351

          dschettl added a comment - Is solved with Hudson 1.351

          dschettl added a comment -

          Problem still exists in 1.359

          dschettl added a comment - Problem still exists in 1.359

          lfischer added a comment -

          The problem still exists in Hudson v1.385 using CVS Plug-In v1.2.

          lfischer added a comment - The problem still exists in Hudson v1.385 using CVS Plug-In v1.2.

          Daniel Beck added a comment -

          Does this issue still occur in recent Jenkins versions (say, not older than 1.532.3)?

          Daniel Beck added a comment - Does this issue still occur in recent Jenkins versions (say, not older than 1.532.3)?

          Daniel Beck added a comment -

          Resolving: No response to comment asking for updated information in over two weeks.

          Due to the age of this issue, please file a new issue if this still occurs on recent Jenkins/Perforce plugin versions.

          Daniel Beck added a comment - Resolving: No response to comment asking for updated information in over two weeks. Due to the age of this issue, please file a new issue if this still occurs on recent Jenkins/Perforce plugin versions.

            Unassigned Unassigned
            dschettl dschettl
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: