[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oleg Nenashev Labels: 2.204.3-fixed 2.204.5-rejected 2.222.1-fixed non-trivial-lts-backporting regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.8831.1584527760310%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oliver Gondža Labels: 2.204.3-fixed 2.204.5-rejected lts 2.222.1 - candidate fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.3974.1583848680301%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick commented on JENKINS-57888 Re: Custom log format broken by 2.177 To be clear, it was not this fix which caused the regressions, but unrelated changes in winstone. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.697.1583507880303%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oliver Gondža commented on JENKINS-57888 Re: Custom log format broken by 2.177 This will be reverted in 2.204.5 as it has caused regressions much more impactfull. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.644.1583505840279%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oliver Gondža Labels: 2.204.3-fixed 2.204.5-rejected lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.636.1583505780357%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oliver Gondža Labels: lts 2.204.3 - candidate fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.9139.1581627360293%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oleg Nenashev Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.6986.1580165041152%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oleg Nenashev updated JENKINS-57888 It was released in 2.218, thanks to Louis-Rémi Paquet! I will mark it as LTS candidate, but it would require Winstone backporting due to the JENKINS-60857 regressions in 5.6. If Oliver Gondža decides it is important enough, I will do such backporting. Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.218 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oleg Nenashev commented on JENKINS-57888 Re: Custom log format broken by 2.177 https://github.com/jenkinsci/jenkins/pull/4452 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.4882.1579862880268%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oleg Nenashev Comment: [https://github.com/jenkinsci/winstone/pull/88] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.4807.1579857480396%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oleg Nenashev commented on JENKINS-57888 Re: Custom log format broken by 2.177 https://github.com/jenkinsci/winstone/pull/88 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.4800.1579857420367%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick updated JENKINS-57888 Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.616.1579193401089%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick started work on JENKINS-57888 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.610.1579193400940%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Louis-Rémi Paquet assigned an issue to Louis-Rémi Paquet Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Louis-Rémi Paquet Assignee: Louis-Rémi Paquet Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.599.1579191600625%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Louis-Rémi Paquet commented on JENKINS-57888 Re: Custom log format broken by 2.177 Yes, that would be possible. I'm wondering, though, why the standard java behavior is overridden. It's not something one would expect. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.434.1579183740555%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick commented on JENKINS-57888 Re: Custom log format broken by 2.177 The new formatter is deliberate. There could be a Winstone option to select an alternate formatter if someone cares to write it, or perhaps just by disabling the new formatter when java.util.logging.config.file is defined. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.8900.1579113300238%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Louis-Rémi Paquet commented on JENKINS-57888 Re: Custom log format broken by 2.177 Is there a workaround to be able to provide a ConsoleHandler formatter? If not, I'll be submitting a PR removing the overriding of it. It will still be possible to set the formatter from the command line or the logging.properties as usual. What do you think? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.8894.1579112940300%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Daniel Beck Component/s: winstone-jetty Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.23647.1559919480450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.23645.1559919480427%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title
Gavin Williams updated an issue
Jenkins / JENKINS-57888
Custom log format broken by 2.177
Change By:
Gavin Williams
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:{code:java}.level=ALLhandlers=java.util.logging.ConsoleHandlerjava.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{code}I've also added the following JVM argument:{code:java}-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties{code} Log format with 2.176:{noformat}[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{noformat} Log format with 2.177:{noformat}2019-06-06 15:11:40.956+ [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2019-06-06 15:11:41.136+ [id=20] INFO hudson.WebAppMain$3#run: Jenkins is fully up and running{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title
Gavin Williams updated an issue
Jenkins / JENKINS-57888
Custom log format broken by 2.177
Change By:
Gavin Williams
Upon upgrading from 2.176 to 2.177, it would appear that support for providing a custom log format has been broken, I suspect by due to what looks like an undocumented [change|[https://github.com/jenkinsci/winstone/pull/63]] in the upgrade of Jetty Winstone library . Logging.properties file:{code:java}.level=ALLhandlers=java.util.logging.ConsoleHandlerjava.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{code}I've also added the following JVM argument:{code:java}-Djava.util.logging.config.file=/var/lib/jenkins/logging.properties{code} Log format with 2.176:{noformat}[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{noformat} Log format with 2.177:{noformat}2019-06-06 15:11:40.956+ [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 2019-06-06 15:11:41.136+ [id=20] INFO hudson.WebAppMain$3#run: Jenkins is fully up and running{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Gavin Williams created an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-06 15:23 Priority: Major Reporter: Gavin Williams Upon upgrading from 2.176 to 2.177, it would appear that support for providing a custom log format has been broken, I suspect by the upgrade of Jetty. 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:
