Setting 0 in the "Number of builds to keep" fields produce strange behavior

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      If you set the number of builds to keep on a project to zero, successfull and
      unstable builds behave right but failed builds are simply ignored (no history,
      no red bullet, nothing ...).

      On a projet with such a setup, when the build fails nothing particular is logged
      but in the build console you get this :

      [HUDSON] Archiving /srv/var/hudson/jobs/dumb/workspace/checkout/pom.xml to
      /srv/var/hudson/jobs/dumb/modules/foo$dumb/builds/2009-07-27_09-27-51/archive/foo/dumb/1.0.0-SNAPSHOT/pom.xml
      [INFO] ------------------------------------------------------------------------
      [ERROR] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Compilation failure
      Failure executing javac, but could not parse the error:
      Fatal Error: Unable to find package java.lang in classpath or bootclasspath

      [INFO] ------------------------------------------------------------------------
      [INFO] For more information, run Maven with the -e switch
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time: 7 seconds
      [INFO] Finished at: Mon Jul 27 09:28:01 UTC 2009
      <html><head><title>Error 404</title></head><body bgcolor="#ffffff"><h1>Status
      Code: 404</h1>Exception: <br>Stacktrace: <pre>(none)
      </pre><br><hr size="1" width="90%"><i>Generated by Winstone Servlet Engine
      v0.9.10 at Mon Jul 27 09:28:02 UTC 2009</i></body></html>

      I don't know how this can be solved, maybe by preventing a value of zero in this
      field.

            Assignee:
            Alan Harder
            Reporter:
            eskatos
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: