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

Test report XMLs cannot cope with spaces in name

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: junit-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      I cannot get Hudson to hook into my Junit reports as where it asks for "Test
      report XMLs" on the config screen cannot cope twith spaces. Replacing space
      with %20 also does not work.

      Example */IAS%202.6.1/artifacts/junit/junit-result/.xml gives error '**/IAS%
      202.6.1/artifacts/junit/junit-result/.xml' doesn't match anything: '*' exists
      but not '**/IAS%202.6.1'

      Example */IAS 2.6.1/artifacts/junit/junit-result/.xml gives error '**/IAS'
      doesn't match anything: '*' exists but not '*/IAS'

      This should be a very easy fix but is a show stopper for junit report
      integration

        Attachments

          Activity

          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          Believe it or not, this is how Ant works, and Hudson was just reusing its code.

          But I think this is more confusing than useful, so as of 1.172 I'm parting way
          from Ant and only using ',' as the pattern separator.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - Believe it or not, this is how Ant works, and Hudson was just reusing its code. But I think this is more confusing than useful, so as of 1.172 I'm parting way from Ant and only using ',' as the pattern separator.
          Hide
          akostadinov akostadinov added a comment -

          That breaks compatibility with current installations. I don't really think
          compatibility should be a show stopper for hudson but some useful improvements
          were rejected due to compatibility with older versions.
          Lets have some policy.

          To me this particular issue is not more important (or much important at all)
          than the initial directory stuff with multiple scm locations. Actually the user
          could avoid using paths with a space in the name which is not smart to have anyways.

          Don't get me wrong. I don't want you to revert the change. I'm asking for a policy.

          btw. another rant - such a change should not go without a changelog entry.

          Show
          akostadinov akostadinov added a comment - That breaks compatibility with current installations. I don't really think compatibility should be a show stopper for hudson but some useful improvements were rejected due to compatibility with older versions. Lets have some policy. To me this particular issue is not more important (or much important at all) than the initial directory stuff with multiple scm locations. Actually the user could avoid using paths with a space in the name which is not smart to have anyways. Don't get me wrong. I don't want you to revert the change. I'm asking for a policy. btw. another rant - such a change should not go without a changelog entry.
          Hide
          ajpurkiss ajpurkiss added a comment -

          I agree spaces in names is a bad thing, unfortunately I had no say in the
          naming in my particualr case, also spaces are a way of life these days more
          often then not so apps should be able to cope with spaces as best they can
          whether that be through wrapping in quotes or whatever the solution is when
          using directory/file names.

          Thanks for the quick turn around by the way. I am looking forward to using
          Hudson within our build process.

          Show
          ajpurkiss ajpurkiss added a comment - I agree spaces in names is a bad thing, unfortunately I had no say in the naming in my particualr case, also spaces are a way of life these days more often then not so apps should be able to cope with spaces as best they can whether that be through wrapping in quotes or whatever the solution is when using directory/file names. Thanks for the quick turn around by the way. I am looking forward to using Hudson within our build process.
          Hide
          ajpurkiss ajpurkiss added a comment -

          Error message still shown even though the link actually works.

          */IAS 2.6.1/artifacts/junit/junit-result/.xml still shows the error message
          on the config screen even though it works fine as far as I can tell now. I
          suspect that this just needs to have the error checking updated to match what
          the backend can now handle.

          Show
          ajpurkiss ajpurkiss added a comment - Error message still shown even though the link actually works. * /IAS 2.6.1/artifacts/junit/junit-result/ .xml still shows the error message on the config screen even though it works fine as far as I can tell now. I suspect that this just needs to have the error checking updated to match what the backend can now handle.
          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          Ouch. Thanks for the catch. Fixed in 1.173.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - Ouch. Thanks for the catch. Fixed in 1.173.

            People

            • Assignee:
              Unassigned
              Reporter:
              ajpurkiss ajpurkiss
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: