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

remove unneccessary stack traces in jenkins log

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • plot-plugin
    • None
    • Jenkins 1.554.2, plot-plugin 1.8

      Parsing should accept unset (empty string) number of builds instead of logging a "severe" problem each time all data is plotted.

      int numBuilds;
try {
	numBuilds = Integer.parseInt(getURLNumBuilds());
} catch (NumberFormatException nfe) {
	LOGGER.log(Level.SEVERE, "Exception converting to integer", nfe);
	numBuilds = Integer.MAX_VALUE;
}

          [JENKINS-25849] remove unneccessary stack traces in jenkins log

          Sebastian Schuberth added a comment -

          I've addressed this as part of this pending PR: https://github.com/jenkinsci/plot-plugin/pull/19

          Sebastian Schuberth added a comment - I've addressed this as part of this pending PR: https://github.com/jenkinsci/plot-plugin/pull/19

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Sebastian Schuberth
          Path:
          src/main/java/hudson/plugins/plot/Plot.java
          http://jenkins-ci.org/commit/plot-plugin/e7bab51199f96a929609eb98db2ff959a13636af
          Log:
          [FIXED JENKINS-25849] Do not log if parsing a blank string to int fails

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Sebastian Schuberth Path: src/main/java/hudson/plugins/plot/Plot.java http://jenkins-ci.org/commit/plot-plugin/e7bab51199f96a929609eb98db2ff959a13636af Log: [FIXED JENKINS-25849] Do not log if parsing a blank string to int fails

            nidaley nidaley
            _men_ Markus
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: