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

different behavior of <space> in job name for nant task after update

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • nant-plugin
    • None
    • Windows 7 Pro SP1 64 bit
      NAnt 0.90 (Build 0.90.3780.0; release; 08.05.2010)
      Jenjins installed on D:\Jenkins\
      no entry in parameter "different workspace path" for all jobs.

    Description

      i have updated jenkins from 1.418 to current version (1.428).
      and nant plugin from 1.4.1 to 1.4.2

      a job with a <space> in the job name now runs into an error running the nant task.

      Job name: "Test job"

      nant options:
      Nant Build File: "$WORKSPACE\build\test.build" (with ")
      Targets: compileFiles

      error:

      invalid character in path ->
      BUILD FAILED
      "D:\Jenkins\jobs\Test:
      Error loading buildfile.
      Illegales Zeichen im Pfad.

      when i replace the <space> with underline:
      BUILD FAILED
      "D:\Jenkins\jobs\Test_job\workspace\build\test.build":
      Error loading buildfile.
      Illegales Zeichen im Pfad.

      when i remove the quotation marks in the nant options:
      BUILD FAILED
      D:\Jenkins\jobs\Test:
      Error loading buildfile.
      Die Datei "D:\Jenkins\jobs\Test" konnte nicht gefunden werden.

      when i replace the job with underline + remove the quotation marks in the nant options:
      works!

      is the job name allowed to contain a <space>? how should i set up the job + nant task?

      i have a different job using "xsltproc.exe". It can't handle a space in the path name (Or i don't handle the path correct in my skript). So i used there job names without spaces (replaced by underline). Is this the way to be done?

      Attachments

        Activity

          jan_goyvaerts Jan Goyvaerts added a comment -

          It seems it depends on the commands the build will invoke on the OS. In Linux still sometimes fails too. Because spaces in the name of the job will be part of the file paths. Sometimes the space is considered as a separator between a command and its arguments. Sometimes not.

          Even if it does look clumsy, better put some other non-space character in the name.

          jan_goyvaerts Jan Goyvaerts added a comment - It seems it depends on the commands the build will invoke on the OS. In Linux still sometimes fails too. Because spaces in the name of the job will be part of the file paths. Sometimes the space is considered as a separator between a command and its arguments. Sometimes not. Even if it does look clumsy, better put some other non-space character in the name.
          danielbeck Daniel Beck added a comment -

          Not a core bug: Core provides facilities for plugins to build Windows-compatible command lines (ArgumentListBuilder.toWindowsCommand()).

          danielbeck Daniel Beck added a comment - Not a core bug: Core provides facilities for plugins to build Windows-compatible command lines ( ArgumentListBuilder.toWindowsCommand() ).

          People

            Unassigned Unassigned
            raller09 Ralf Moorbrink
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: