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

reduceLog checkbox not available in Process xUnit test result report

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Component/s: xunit-plugin
    • Labels:
      None
    • Environment:
      xunit-plugin 2.3.3
    • Similar Issues:

      Description

      New reduceLog setting changes default behavior, and if plugin is being used as a Build Step there is no way to restore the old behavior through the GUI.  If the plugin is used as Post-build Action, the GUI does show the new checkbox under Advanced.

      Looking at the source, the setting was added to

      src/main/resources/org/jenkinsci/plugins/xunit/XUnitPublisher

      but not to

      src/main/resources/org/jenkinsci/plugins/xunit/XUnitBuilder

      The two sets of settings look to like they should be the same.  Adding the new checkbox  and properties to the XUnitBuilder resources gives the desired result, but if the settings are intended to be identical, combining these to a single point of maintenance would be preferable.  As it is, the title and description for the report time margin are also out of sync between the two.

       

       

        Attachments

          Activity

          Hide
          nfalco Nikolas Falco added a comment -

          The reason is because the builder is deprecated. I left just to be back compatible for people that had written pipeline using step($class: XUnitBuilder,...)

          It can use only default configuration that prevents OOM in jenkins (the same of JUnit plugins)

          Show
          nfalco Nikolas Falco added a comment - The reason is because the builder is deprecated. I left just to be back compatible for people that had written pipeline using step($class: XUnitBuilder,...) It can use only default configuration that prevents OOM in jenkins (the same of JUnit plugins)
          Hide
          lizzardo Steven Wadsworth added a comment -

          It would have been helpful to better announce the change in default behavior and the deprecation of Builder.  The jobs I have set up all use the xUnit plugin as a build step, not a post-build step, and information necessary to debug failed tests was unexpectedly missing. Set up this way, there is no way to return to previous behavior. 

          I have not written this into any pipelines, so had no direct visibility of Builder vs. Publisher, and I try to look at all changelogs before updating plugins.

          We were not experiencing the OOM.

          Show
          lizzardo Steven Wadsworth added a comment - It would have been helpful to better announce the change in default behavior and the deprecation of Builder.  The jobs I have set up all use the xUnit plugin as a build step, not a post-build step, and information necessary to debug failed tests was unexpectedly missing. Set up this way, there is no way to return to previous behavior.  I have not written this into any pipelines, so had no direct visibility of Builder vs. Publisher, and I try to look at all changelogs before updating plugins. We were not experiencing the OOM.

            People

            Assignee:
            nfalco Nikolas Falco
            Reporter:
            lizzardo Steven Wadsworth
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: