3 Replies Latest reply on Apr 17, 2009 1:52 PM by Clebert Suconic

    JUnit Reports...

    Clebert Suconic Master

      hudson-reports is aways generating the JUnitReports, and the report will take some space on hudson in a hourly base, even though the report is never looked (Hudson provides its own reporting). So, I would like to remove the compile-reports call from hudson-reports.

      I would like to also update junit-frames.xsl with the one provided by ant. The xsl we use is years old and exists since JBoss3. If we get a newer one we will have the System.out report (which I find it useful).


      Any thoughts or contrary opinions?

        • 1. Re: JUnit Reports...
          Clebert Suconic Master

          I have then removed the compile-reports call from hudson-tests.

          As I said before that is only consuming disk-space on hudson servers, since hudson provides its own report.

          If you mind about typing "ant compile-reports" every time after a build, we could create another target such as dev-tests.. or whatever.


          I've also updated the xsl. the colors are different, but it brings more information. If you guys prefer the old version we can just revert the xsl change at /tests/src/stylesheets/junit-frames.xsl. (I have also removed a bunch of non-used files on the same dir).

          • 2. Re: JUnit Reports...
            Tim Fox Master

            Please create another target so we don't have to type ant compile-reports when we run them locally.

            • 3. Re: JUnit Reports...
              Clebert Suconic Master

               

              "timfox" wrote:
              Please create another target so we don't have to type ant compile-reports when we run them locally.


              Ok, from now on we type this at our boxes:

              ant dev-tests



              and hudson-tests is only meant for hudson (as the name states)