-
Bug
-
Resolution: Fixed
-
Major
-
-
Jenkins 2.218
Upon upgrading from 2.176 to 2.177, it would appear that support for providing a custom log format has been broken, due to what looks like an undocumented change (https://github.com/jenkinsci/winstone/pull/63) in the Winstone library.
Logging.properties file:
.level=ALL handlers=java.util.logging.ConsoleHandler java.util.logging.SimpleFormatter.format=[%1$tF %1$tT.%1$tL][%4$s][%2$s] %5$s %6$s%n java.util.logging.ConsoleHandler.level=INFO java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
I've also added the following JVM argument:
-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties
Log format with 2.176:
[2019-06-06 15:10:07.881][INFO][jenkins.InitReactorRunner$1 onAttained] Completed initialization [2019-06-06 15:10:08.052][INFO][hudson.WebAppMain$3 run] Jenkins is fully up and running
Log format with 2.177:
2019-06-06 15:11:40.956+0000 [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2019-06-06 15:11:41.136+0000 [id=20] INFO hudson.WebAppMain$3#run: Jenkins is fully up and running
- causes
-
JENKINS-60857 Wildcard certificates rejected by Winstone after Jetty update
- Closed
- links to