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

Can't configure report pattern in job configuration UI

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • dtkit-plugin, xunit-plugin
    • None
    • Operating System: Server RHEL 7.6, Client Centos 7, Win10
      JDK/JRE: OpenJDK Runtime Environment 1.8.0_191-b12
      Jenkins 2.181 and xUnit 2.3.5 ran directly
      No reverse proxy
      Firefox 60.7.0esr
    • 2.1.1-1

      When configuring a xUnit post build action it is not possible to configure a pattern for report files. Adding a <pattern> element manually in config.xml works, but gets overwritten each time you use the job configuration page.

      I have added an image of the configuration page

       

       

        1. JenkinsxUnit.JPG
          JenkinsxUnit.JPG
          48 kB

          [JENKINS-58089] Can't configure report pattern in job configuration UI

          Ukon GOTO added a comment -

          I have the same problem with the report type JUnit.

          With version 2.3.4 is OK

          This problem appears only with version 2.3.5 :

          The fields "Pattern" and options disappeared

          If we modified a field Thresholds in a existing job we lost the pattern in the configuration.xml file of the job. And the xunit part of the job no longer works we have "INFO: Skipping tests recording." in the job's logs

          Ukon GOTO added a comment - I have the same problem with the report type JUnit. With version 2.3.4 is OK This problem appears only with version 2.3.5 : The fields "Pattern" and options disappeared If we modified a field Thresholds in a existing job we lost the pattern in the configuration.xml file of the job. And the xunit part of the job no longer works we have "INFO: Skipping tests recording." in the job's logs

          Nikolas Falco added a comment -

          I can reproduce this issue in our production environment but I can not in development (mvn hpi:run). I do not know what happens in production, why descriptor jelly files are not taken up.

          Nikolas Falco added a comment - I can reproduce this issue in our production environment but I can not in development (mvn hpi:run). I do not know what happens in production, why descriptor jelly files are not taken up.

          Sagar Khushalani added a comment -

          Can confirm on Jenkins v2.176.1 with version 2.3.5

          Sagar Khushalani added a comment - Can confirm on Jenkins v2.176.1 with version 2.3.5

          Nikolas Falco added a comment -

          Fix released in DTKit API plugin 2.1.1-1. Jelly file for tools are moved there. Tested in our production environment.

          Nikolas Falco added a comment - Fix released in DTKit API plugin 2.1.1-1. Jelly file for tools are moved there. Tested in our production environment.

          Pieter-Jan Busschaert added a comment -

          Can somebody please write a changelog entry for that DTKit update that mentions this issue?
          I had the same problem and it took a while (until finding this issue) that the DTKit update might be related.
          Even better: make the xUnit plugin depend on that updated version of the DTKit plugin?

          (I typically wait to update plugins if I can't find a changelog entry for the update)

          Pieter-Jan Busschaert added a comment - Can somebody please write a changelog entry for that DTKit update that mentions this issue? I had the same problem and it took a while (until finding this issue) that the DTKit update might be related. Even better: make the xUnit plugin depend on that updated version of the DTKit plugin? (I typically wait to update plugins if I can't find a changelog entry for the update)

            nfalco Nikolas Falco
            gerrietr Gerriet Reents
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: