http://github.com/jenkinsci/winstone/commit/26c7de06a9be7eea8d2c959f0366b2d287d99388 changed logging framework to use java.util.logger, then level switched from (1:9) range to (Integer.MIN_VALUE:MAX_VALUE).
setting JENKINS_DEBUG_LEVEL to 5 in jenkins sysconif, expecting INFO, result in FINEST logging.
actual impact on jenkins probably was hidden by JENKINS-16952.
Originally reported by 
ndeloof, imported from: winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
- status: Resolved
- priority: Major
- component(s): core
- label(s): 1.509.3-fixed
- resolution: Fixed
- resolved: 2013-07-17T15:16:08+00:00
- votes: 0
- watchers: 4
- imported: 2025-11-24
Raw content of original issue
http://github.com/jenkinsci/winstone/commit/26c7de06a9be7eea8d2c959f0366b2d287d99388 changed logging framework to use java.util.logger, then level switched from (1:9) range to (Integer.MIN_VALUE:MAX_VALUE).
setting JENKINS_DEBUG_LEVEL to 5 in jenkins sysconif, expecting INFO, result in FINEST logging.
actual impact on jenkins probably was hidden by JENKINS-16952.
http://github.com/jenkinsci/winstone/commit/26c7de06a9be7eea8d2c959f0366b2d287d99388 changed logging framework to use java.util.logger, then level switched from (1:9) range to (Integer.MIN_VALUE:MAX_VALUE).
setting JENKINS_DEBUG_LEVEL to 5 in jenkins sysconif, expecting INFO, result in FINEST logging.
actual impact on jenkins probably was hidden by
JENKINS-16952.Originally reported by
ndeloof, imported from: winstone don't use (1:9) range for loglevels for JENKINS_DEBUG_LEVEL
Raw content of original issue