[JIRA] (JENKINS-61519) Odd rendering of Monitoring of Jenkins master plugin in Manage Jenkins screen
Title: Message Title
evernat edited a comment on JENKINS-61519
Re: Odd rendering of Monitoring of Jenkins master plugin in Manage Jenkins screen
There are 3 html tags on "Monitoring of Jenkins master":{code:java}Monitoring of Jenkins masterMonitoring of memory, cpu, http requests and more in Jenkins master.You can also view the monitoring of builds, build queue and Jenkins nodes.{code}The other management links in the page have only the first one.Given that the view is AFAIK in [ manage.jelly |https : //github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/model/Jenkins/manage.jelly]: {code:java} ${m.displayName} {code}and given that the ManagementLink code is https://github.com/jenkinsci/monitoring-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/monitoring/PluginManagementLink.javahow can it print 3 html tags?
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.205215.1584580258000.10793.1584888960190%40Atlassian.JIRA.
[JIRA] (JENKINS-61519) Odd rendering of Monitoring of Jenkins master plugin in Manage Jenkins screen
Title: Message Title
evernat commented on JENKINS-61519
Re: Odd rendering of Monitoring of Jenkins master plugin in Manage Jenkins screen
There are 3 html tags on "Monitoring of Jenkins master":
"manage-option manage-page__column">
"/monitoring" title="Monitoring of Jenkins master">"/static/163b9cff/images/48x48/monitor.gif" alt="manage-option" class="icon">
"/monitoring" title="Monitoring of Jenkins master">Monitoring of Jenkins master
"/monitoring" title="Monitoring of Jenkins master">Monitoring of memory, cpu, http requests and more in Jenkins master."./monitoring/nodes">You can also view the monitoring of builds, build queue and Jenkins nodes.
The other management links in the page have only the first one. Given that the view is AFAIK in manage.jelly:
"${m.urlName}" title="${m.displayName}">
"icon" src="" class="code-quote" style="color: #009100">"${iconUrl}" alt="manage-option"/>
${m.displayName}
"${m.description}"/>
"${m}" page="info.jelly" optional="true"/>
and given that the ManagementLink code is https://github.com/jenkinsci/monitoring-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/monitoring/PluginManagementLink.java how can it print 3 html tags?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60771) "Country" column is misleading
Title: Message Title evernat edited a comment on JENKINS-60771 Re: "Country" column is misleading Technically, it's true than the displayed country flag is based on the browser's locale, like technically [Edge is now based on Chrome|https://issues.jenkins-ci.org/browse/JENKINS-60772]. But it's called Edge and not Chrome.First, the column is written as Country because there is no translation of Locale in French :).And then and it's more important, the displayed country flag is only the country part of the browser's locale. Most of the time, that is the real country and location of the user, or at least of his/her citizenship. And of course, a country flag is about a country, not about a locale.Given that, closing this issue as invalid.For GeoIP, I understand that having country or and city location of users may be of interest but that's another issue. 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.204032.1579035588000.117.1579139040158%40Atlassian.JIRA.
[JIRA] (JENKINS-60771) "Country" column is misleading
Title: Message Title evernat closed an issue as Not A Defect Jenkins / JENKINS-60771 "Country" column is misleading Change By: evernat Status: Open Closed Resolution: Not A Defect 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.204032.1579035588000.114.1579138920332%40Atlassian.JIRA.
[JIRA] (JENKINS-60771) "Country" column is misleading
Title: Message Title evernat commented on JENKINS-60771 Re: "Country" column is misleading Technically, it's true than the displayed country flag is based on the browser's locale, like technically Edge is now based on Chrome. But it's called Edge and not Chrome. First, the column is written as Country because there is no translation of Locale in French . And then and it's more important, the displayed country flag is only the country part of the browser's locale. Most of the time, that is the real country and location of the user, or at least of his/her citizenship. And of course, a country flag is about a country, not about a locale. Given that, closing this issue as invalid. For GeoIP, I understand that having country or city location of users may be of interest but that's another issue. 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.204032.1579035588000.111.1579138860225%40Atlassian.JIRA.
[JIRA] (JENKINS-60772) Microsoft Edge identified as Chrome
Title: Message Title evernat updated JENKINS-60772 Jenkins / JENKINS-60772 Microsoft Edge identified as Chrome Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed 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.204033.1579035877000.8785.1579099680307%40Atlassian.JIRA.
[JIRA] (JENKINS-60772) Microsoft Edge identified as Chrome
Title: Message Title evernat commented on JENKINS-60772 Re: Microsoft Edge identified as Chrome Identifying the new Microsoft Edge as a Chrome browser is not really false, as Edge says itself in its user-agent. By the way, I see that the given user agent example is Edge on Linux. Anyway, it's fixed now in javamelody-core and will be released in 1.82. 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.204033.1579035877000.8782.1579099620481%40Atlassian.JIRA.
[JIRA] (JENKINS-60433) Version 1.80.0 throws JEP-200 error
Title: Message Title evernat updated JENKINS-60433 Thanks for the issue. It's fixed by https://github.com/jenkinsci/monitoring-plugin/commit/2712582481807bce64a6137994f7c8f7c094080e and ready for the next release (1.81). Jenkins / JENKINS-60433 Version 1.80.0 throws JEP-200 error Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat updated JENKINS-58419 Jenkins / JENKINS-58419 CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Change By: evernat Status: Fixed but Unreleased Closed 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.200546.1562746885000.1514.1564100340873%40Atlassian.JIRA.
[JIRA] (JENKINS-58388) `report` link in monitoring plugin description doesn't work
Title: Message Title evernat updated JENKINS-58388 Jenkins / JENKINS-58388 `report` link in monitoring plugin description doesn't work Change By: evernat Status: Fixed but Unreleased Closed 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.200512.1562601973000.1518.1564100341584%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat updated JENKINS-58419 Jenkins / JENKINS-58419 CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed 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.200546.1562746885000.658.1564048800472%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat commented on JENKINS-58419 Re: CAS: No redirect after login after updating Monitoring plugin to 1.78.0 Fixed by 068775a, to be released in 1.79 (soon) 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.200546.1562746885000.655.1564048800422%40Atlassian.JIRA.
[JIRA] (JENKINS-58419) CAS: No redirect after login after updating Monitoring plugin to 1.78.0
Title: Message Title evernat commented on JENKINS-58419 Re: CAS: No redirect after login after updating Monitoring plugin to 1.78.0 It may be related to this commit for this issue in javamelody-core. To be sure, I have made a new build without the commit. You can download it from http://javamelody.org/downloads/monitoring.hpi and install using the Jenkins plugin manager. Can you check if this build works around the issue? 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.200546.1562746885000.17828.1563803880223%40Atlassian.JIRA.
[JIRA] (JENKINS-57373) monitoring-plugin description in manage jenkins looks wrong
Title: Message Title evernat updated JENKINS-57373 released in 1.78.0 Jenkins / JENKINS-57373 monitoring-plugin description in manage jenkins looks wrong Change By: evernat Status: Fixed but Unreleased Closed 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.199154.1557323762000.17825.1563802680309%40Atlassian.JIRA.
[JIRA] (JENKINS-58388) `report` link in monitoring plugin description doesn't work
Title: Message Title evernat updated JENKINS-58388 Reproduced in the Available and Updated tabs of plugin manager. This link works in the Installed tab after install, but it is currently escaped and broken when it comes from the update center (http://updates.jenkins-ci.org/update-center.json). Fixed by https://github.com/jenkinsci/monitoring-plugin/commit/d6187c616b4d1eefcbacde9b580e4c0bfff1d0c3 Jenkins / JENKINS-58388 `report` link in monitoring plugin description doesn't work Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-57373) monitoring-plugin description in manage jenkins looks wrong
Title: Message Title evernat updated JENKINS-57373 Jenkins / JENKINS-57373 monitoring-plugin description in manage jenkins looks wrong Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed 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.199154.1557323762000.21359.1557357720187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57373) monitoring-plugin description in manage jenkins looks wrong
Title: Message Title evernat commented on JENKINS-57373 Re: monitoring-plugin description in manage jenkins looks wrong Fixed by https://github.com/jenkinsci/monitoring-plugin/commit/eb2086790605d11504287496c82b063cb17a2be8 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.199154.1557323762000.21356.1557357120114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57373) monitoring-plugin description in manage jenkins looks wrong
Title: Message Title
evernat edited a comment on JENKINS-57373
Re: monitoring-plugin description in manage jenkins looks wrong
Yes, I know this issue. Thanks for reminding it to me.With the following description in PluginManagementLink, it is better now:{{"Monitoring of memory, cpu, http requests and more in Jenkins master."}}{{ + "You can also view the monitoring of builds, build queue and Jenkins nodes."}}See this screenshot:!management links.png!It is not immediately obvious but the two first lines have a link to the "/monitoring" page.And the third line has a link to the "/monitoring/nodes" page.
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.199154.1557323762000.21222.1557353820228%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57373) monitoring-plugin description in manage jenkins looks wrong
Title: Message Title
evernat commented on JENKINS-57373
Re: monitoring-plugin description in manage jenkins looks wrong
Yes, I know this issue. Thanks for reminding it to me. With the following description in PluginManagementLink, it is better now: "Monitoring of memory, cpu, http requests and more in Jenkins master." {{ + "You can also view the monitoring of builds, build queue and Jenkins nodes."}} See this screenshot: It is not immediately obvious but the two first lines have a link to the "/monitoring" page. And the third line has a link to the "/monitoring/nodes" page.
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.199154.1557323762000.21219.1557353760170%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57373) monitoring-plugin description in manage jenkins looks wrong
Title: Message Title evernat updated an issue Jenkins / JENKINS-57373 monitoring-plugin description in manage jenkins looks wrong Change By: evernat Attachment: management links.png 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.199154.1557323762000.21216.1557353640178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21695) IllegalStateException: WRITER masks original exception
Title: Message Title evernat commented on JENKINS-21695 Re: IllegalStateException: WRITER masks original exception Daniel Beck Not really a different issue. The problem is the same and the fix which was added using response.isCommitted() does not work anymore as seen in the stack-trace of JENKINS-55006. (I suppose that the fix was working last year.) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat edited a comment on JENKINS-55006 Re: /monitoring/nodes?format=prometheus throws error 500 I can't reproduce the issue in Jenkins 1.251 with monitoring plugin 1.74.There is a root cause exception indeed, but the problem is that Jenkins fails to give you this root cause exception and the stack-trace is of its failure to report the exception. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat commented on JENKINS-55006 Re: /monitoring/nodes?format=prometheus throws error 500 So I have reopened https://issues.jenkins-ci.org/browse/JENKINS-21695 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21695) IllegalStateException: WRITER masks original exception
Title: Message Title evernat reopened an issue In Jenkins 2.138.3 and upgraded Jetty, testing response.isCommitted() does not seem enough to fix this issue. See https://issues.jenkins-ci.org/browse/JENKINS-55006 A catch instead of response.isCommitted() may be needed? Jenkins / JENKINS-21695 IllegalStateException: WRITER masks original exception Change By: evernat Resolution: Fixed Status: Resolved Reopened 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat commented on JENKINS-55006 Re: /monitoring/nodes?format=prometheus throws error 500 I can't reproduce the issue in Jenkins 1.251 with monitoring plugin 1.74. There is a root cause exception indeed, but the problem is that Jenkins fails to give you this root cause exception and the stack-trace of its failure to report the exception. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat updated an issue Jenkins / JENKINS-55006 /monitoring/nodes?format=prometheus throws error 500 Change By: evernat Accessing /monitoring/nodes?format=prometheus gives error 500 Error: _java java .lang.IllegalStateException: WRITER_ WRITER _at at org.eclipse.jetty.server.Response.getOutputStream( [ Response.java:917 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.eclipse.jetty.server.Response#917] ) _ _at at javax.servlet.ServletResponseWrapper.getOutputStream( [ ServletResponseWrapper.java:142 |http://ci.corp.atmel.com/mcu/monitoring?part=source=javax.servlet.ServletResponseWrapper#142] ) _ _at at org.kohsuke.stapler.compression.CompressionServletResponse.activate( [ CompressionServletResponse.java:61 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.compression.CompressionServletResponse#61] ) _ _at at org.kohsuke.stapler.compression.CompressionFilter.activate( [ CompressionFilter.java:108 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.compression.CompressionFilter#108] ) _ _at at org.kohsuke.stapler.ResponseImpl.getCompressedOutputStream( [ ResponseImpl.java:302 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.ResponseImpl#302] ) _ _at at org.kohsuke.stapler.jelly.DefaultScriptInvoker.createOutputStream( [ DefaultScriptInvoker.java:88 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.DefaultScriptInvoker#88] ) _ _at at org.kohsuke.stapler.jelly.DefaultScriptInvoker.createXMLOutput( [ DefaultScriptInvoker.java:68 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.DefaultScriptInvoker#68] ) _ _at at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript( [ DefaultScriptInvoker.java:51 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.DefaultScriptInvoker#51] ) _ _at at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch( [ JellyFacet.java:103 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.JellyFacet$1#103] ) _ _at at org.kohsuke.stapler.Stapler.tryInvoke( [ Stapler.java:739 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.Stapler#739] ) _ _at at org.kohsuke.stapler.Stapler.invoke( [ Stapler.java:870 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.Stapler#870] ) _ _at at org.kohsuke.stapler.Stapler.invoke( [ Stapler.java:668 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.Stapler#668] ) _ _at at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0( [ InstallUncaughtExceptionHandler.java:36 |http://ci.corp.atmel.com/mcu/monitoring?part=source=hudson.init.impl.InstallUncaughtExceptionHandler#36] ) _ _at at org.kohsuke.stapler.compression.CompressionFilter.reportException( [ CompressionFilter.java:77
[JIRA] (JENKINS-54371) Monitoring plugin not pushing slave metrics to InfluxDB
Title: Message Title evernat updated JENKINS-54371 See https://github.com/javamelody/javamelody/issues/791 Jenkins / JENKINS-54371 Monitoring plugin not pushing slave metrics to InfluxDB Change By: evernat Status: Open Fixed but Unreleased Resolution: Done 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54371) Monitoring plugin not pushing slave metrics to InfluxDB
Title: Message Title evernat updated JENKINS-54371 Jenkins / JENKINS-54371 Monitoring plugin not pushing slave metrics to InfluxDB Change By: evernat Status: Fixed but Unreleased Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Nelu Vasilica Any news? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42112) HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth)
Title: Message Title evernat edited a comment on JENKINS-42112 Re: HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth) Given the screenshot, I suppose that you mean Google login plugin and not Google Authorization plugin.And thanks for the issue, this is fixed now : the user displayed is now the email of the user when using Google login plugin . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42112) HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth)
Title: Message Title evernat commented on JENKINS-42112 Re: HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth) Given the screenshot, I suppose that you mean Google login plugin and not Google Authorization plugin. And thanks for the issue, this is fixed now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42112) HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth)
Title: Message Title evernat updated an issue Jenkins / JENKINS-42112 HTTP user session is reported as anonymous when using anything but AbstractPasswordBasedSecurityRealm(like google auth) Change By: evernat The user generated in the HTTP session section reports as anonymous when using non-username/password style login methods.Steps to reproduce:1. Download the Google login plugin -Google Authorization plugin - 2. Create a google authorization login(Screen Shot 2017-02-16 at 11.41.05 AM.png)3. Login with said google account4. Check the monitoring page under http sessions5. Observe anonymous user(Screen Shot 2017-02-16 at 11.37.53 AM.png)This also affects the Cloudbees Operations Center to Enterprise communication where the Enterprise version shows anonymous user because it uses a token as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-41394) Remove donate button on monitoring page
Title: Message Title evernat commented on JENKINS-41394 Re: Remove donate button on monitoring page The button is displayed in the javamelody monitoring page. So I think it is clear enough that donations goes for supporting javamelody and/or the monitoring plugin (that's the same basket). Moreover, clicking the button goes to https://github.com/javamelody/javamelody/wiki/Donate which clarifies more. (As a side note, the church was just an example. I prefer to not have any religion, like many people in inland France for historical reasons.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41394) Remove donate button on monitoring page
Title: Message Title evernat edited a comment on JENKINS-41394 Re: Remove donate button on monitoring page Hi Ralph,The Donate button goes to the donate page:https://github.com/javamelody/javamelody/wiki/DonateAs you can see in that page, donations are not many.But they are helpful to pay for backup hardware and for hosting (javamelody.org/stats and demo).The clients finding the hosted jenkins server, your job and this plugin useful don't pay you for a work well done?Do you know that all that work on the plugin and on javamelody was done for free (like in zero salary involved), except a few dollars in donations? I don't think that it is ethical to remove the donate button. When you go to church or to charities, you don't ask to hide the basket to give money I suppose? (In your country I don't know, but in France there is a basket in churches.)That said, you can submit pull requests for bugs and enhancements:https://github.com/javamelody/javamelody/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancementhttps://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20component%20%3D%20monitoring-plugin- Emeric Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41394) Remove donate button on monitoring page
Title: Message Title evernat resolved as Won't Do Jenkins / JENKINS-41394 Remove donate button on monitoring page Change By: evernat Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41394) Remove donate button on monitoring page
Title: Message Title evernat commented on JENKINS-41394 Re: Remove donate button on monitoring page Hi Ralph, The Donate button goes to the donate page: https://github.com/javamelody/javamelody/wiki/Donate As you can see in that page, donations are not many. But they are helpful to pay for backup hardware and for hosting (javamelody.org/stats and demo). The clients finding your job and this plugin useful don't pay you for a work well done? Do you know that all that work on the plugin and on javamelody was done for free (like in zero salary involved), except a few dollars in donations? I don't think that it is ethical to remove the donate button. When you go to church or to charities, you don't ask to hide the basket to give money I suppose? (In your country I don't know, but in France there is a basket in churches.) That said, you can submit pull requests for bugs and enhancements: https://github.com/javamelody/javamelody/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20component%20%3D%20monitoring-plugin Emeric Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit
[JIRA] (JENKINS-37625) exception in logs when hitting /monitoring?action=gc
Title: Message Title evernat assigned an issue to Unassigned Jenkins / JENKINS-37625 exception in logs when hitting /monitoring?action=""> Change By: evernat Component/s: winstone-jetty Component/s: monitoring-plugin Assignee: evernat Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37625) exception in logs when hitting /monitoring?action=gc
Title: Message Title
evernat commented on JENKINS-37625
Re: exception in logs when hitting /monitoring?action="">
For related info: http://stackoverflow.com/questions/41191519/fail-to-get-views-config-xml-via-python-requests-to-secure-jenkins-self-signed Alex Gray: Do you have some "user:password" in the url called from the script? Anyway, I don't think that this is an issue of the monitoring plugin. I think it is an issue of the winstone SimpleAccessLogger: that logger calls Request.getRemoteUser() at some point which calls authenticate and Request.getSession(true). And so the monitoring plugin probably can't do anything about it. Alex Gray: If you can, I suggest to execute a system groovy script inside a Jenkins job instead of calling the /monitoirng?action="" URL. The script for GC would be:
import net.bull.javamelody.*;
before = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory();
System.gc();
after = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory();
println I18N.getFormattedString("ramasse_miette_execute", Math.round((before - after) / 1024));
For that you will need the groovy plugin. And you can see the documentation with several monitoring scripts
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-37625) exception in logs when hitting /monitoring?action=gc
Title: Message Title
evernat edited a comment on JENKINS-37625
Re: exception in logs when hitting /monitoring?action="">
For related info:http://stackoverflow.com/questions/41191519/fail-to-get-views-config-xml-via-python-requests-to-secure-jenkins-self-signed[~grayaii]: Do you have some "user:password" in the url called from the script?Anyway, I don't think that this is an issue of the monitoring plugin. I think it is an issue of the winstone SimpleAccessLogger: that logger calls Request.getRemoteUser() at some point which calls authenticate and Request.getSession(true). And so the monitoring plugin probably can't do anything about it.[~grayaii]: If you can, I suggest as a workaround to execute a system groovy script inside a Jenkins job instead of calling the / monitoirng monitoring ?action="" URL. The script for GC would be:{code:java}import net.bull.javamelody.*;before = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory();System.gc();after = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory();println I18N.getFormattedString("ramasse_miette_execute", Math.round((before - after) / 1024));{code}For that you will need the [groovy plugin|https://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin].And you can see the [documentation with several monitoring scripts|https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+Scripts]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-37625) exception in logs when hitting /monitoring?action=gc
Title: Message Title
evernat edited a comment on JENKINS-37625
Re: exception in logs when hitting /monitoring?action="">
For related info:http://stackoverflow.com/questions/41191519/fail-to-get-views-config-xml-via-python-requests-to-secure-jenkins-self-signed[~grayaii]: Do you have some "user:password" in the url called from the script?Anyway, I don't think that this is an issue of the monitoring plugin. I think it is an issue of the winstone SimpleAccessLogger: that logger calls Request.getRemoteUser() at some point which calls authenticate and Request.getSession(true). And so the monitoring plugin probably can't do anything about it.[~grayaii]: If you can, I suggest as a workaround to execute a system groovy script inside a Jenkins job instead of calling the /monitoirng?action="" URL. The script for GC would be:{code:java}import net.bull.javamelody.*;before = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory();System.gc();after = Runtime.getRuntime().totalMemory() - Runtime.getRuntime().freeMemory();println I18N.getFormattedString("ramasse_miette_execute", Math.round((before - after) / 1024));{code}For that you will need the [groovy plugin|https://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin].And you can see the [documentation with several monitoring scripts|https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+Scripts]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring It's very strange that log4j.jar file in the tomcat directory. Anyway, you probably have old versions of log4j-over-slf4j and of slf4j-api in your classpath. See https://github.com/javamelody/javamelody/issues/566 To fix the issue, you should not have obsolete versions of log4j-over-slf4j and of slf4j-api. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37625) exception in logs when hitting /monitoring?action=gc
Title: Message Title evernat commented on JENKINS-37625 Re: exception in logs when hitting /monitoring?action=""> I have not reproduced the issue using Jenkins 2.21 and monitoring plugin 1.61.0. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34794) Jenkins doesn't start because of NPE
Title: Message Title evernat commented on JENKINS-34794 Re: Jenkins doesn't start because of NPE Hi Bruce, In fact, it was released just 2 hours before you ask. The plugin should be available in your update center now or in 24h. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-34794) Jenkins doesn't start because of NPE
Title: Message Title evernat commented on JENKINS-34794 Re: Jenkins doesn't start because of NPE It seems that either Jenkins.getInstance().getPlugin(org.jvnet.hudson.plugins.monitoring.PluginImpl.class) returns null or PluginImpl.start() is not called by Jenkins. PluginImpl is supposed to be initialized by Jenkins because PluginImpl extends Plugin. How to reproduce the issue? And what version of Jenkins was used? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat resolved as Not A Defect ok, thanks Jenkins / JENKINS-32441 SEVERE: Failed Loading plugin monitoring Change By: evernat Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat edited a comment on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Here are the libs in your plugins in the attached text file [^libs_in_those_plugins.txt], ignoring your plugins versions.There are 2 of your plugins including log4j: violations.hpi and testflight.hpi (both are including log4j v1.2.9).I am not totally convinced that one of those 2 plugins are the cause of the issue, so to find the cause I suggest to try:- install a new version of the monitoring plugin, after removing /WEB-INF/lib/slf4j-api-1.6.3.jar from the hpi file. (I am not convinced that it will fix the issue either, but who knows ? slf4j is not really needed in the plugin anyway.)- uninstall violations.hpi and testflight.hpi- say here what is your servlet container. Is it the default winstone/jetty or tomcat or jboss ?- do you have some log4j file directly in your server container ? (tomcat/lib/ for example)- otherwise I don't know, except that you have many many plugins (107 in fact) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat edited a comment on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Here are the libs in your plugins in the attached [^libs_in_those_plugins. txt file ] , ignoring your plugins versions.There are 2 of your plugins including log4j: violations.hpi and testflight.hpi (both are including log4j v1.2.9).I am not totally convinced that one of those 2 plugins are the cause of the issue, so to find the cause I suggest to try:- install a new version of the monitoring plugin, after removing /WEB-INF/lib/slf4j-api-1.6.3.jar from the hpi file. (I am not convinced that it will fix the issue either, but who knows ? slf4j is not really needed in the plugin anyway.)- uninstall violations.hpi and testflight.hpi- say here what is your servlet container. Is it the default winstone/jetty or tomcat or jboss ?- do you have some log4j file directly in your server container ? (tomcat/lib/ for example)- otherwise I don't know, except that you have many many plugins (107 in fact) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat updated an issue Jenkins / JENKINS-32441 SEVERE: Failed Loading plugin monitoring Here are the libs in your plugins in the attached txt file, ignoring your plugins versions. There are 2 of your plugins including log4j: violations.hpi and testflight.hpi (both are including log4j v1.2.9). I am not totally convinced that one of those 2 plugins are the cause of the issue, so to find the cause I suggest to try: install a new version of the monitoring plugin, after removing /WEB-INF/lib/slf4j-api-1.6.3.jar from the hpi file. (I am not convinced that it will fix the issue either, but who knows ? slf4j is not really needed in the plugin anyway.) uninstall violations.hpi and testflight.hpi say here what is your servlet container. Is it the default winstone/jetty or tomcat or jboss ? do you have some log4j file directly in your server container ? (tomcat/lib/ for example) otherwise I don't know, except that you have many many plugins (107 in fact) Change By: evernat Attachment: libs_in_those_plugins.txt Add Comment
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title evernat resolved as Fixed I think that a file in the storage directories (/auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring/**) was corrupted somewhere in the middle of the file. And that javamelody / jrobin can't read it anymore. You can try to find if ".rrd" file(s) in the storage directories do not have the same size as the others and to delete it. But what is strange is that corruption seems intermittent: from 7:02 to 7:13 and from 8:21 to 8:33 but nothing the day before. Anyway, I have added a catch in the code to auto-reset the file in this case. (2eff216) And 1.59 release is planned soon including that fix. Jenkins / JENKINS-33050 Monitoring stopped working - exception collecting data Change By: evernat Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Can you give the list of all your plugins? I am wondering if one of the plugins includes something like Log4J. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring It seems to be a classloader issue with some Log4J jar file. What other plugins are installed ? Is it reproduced if you restart Jenkins ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title evernat updated an issue Jenkins / JENKINS-20947 Failed to monitor for Free Swap Space Change By: evernat Component/s: monitoring-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title evernat commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data And also can you copy here the "debugging logs" which are displayed at the botton of the /monitoring page? Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title evernat commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data Yes, what is the plugin version? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat updated an issue Jenkins / JENKINS-31035 Introduce a policy for API deprecation Change By: evernat h1. Problem definitionCurrently, we have no backward compatibility policy besides ["compatibility matters"|https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Compatibilitymatters]. With 1000+ plugins and basically the entire core being available to plugins, a lot of difficult or impossible to remove cruft has accumulated over the last ten years. This limits both what can be changed in core, and makes documentation difficult to use for plugin developers.Elaborate solutions such as the bytecode compatibility transformer currently (Oct 2015) introduce difficult to investigate bugs that result in things breaking for users.h1. ProposalLimit the availability in APIs (classes, methods, fields, …) provided by core to a number of releases. Depending on the feature, this can range from a few months, to a few years (e.g. two years being about 100 releases of Jenkins and eight LTS baselines).This deprecation policy needs to be supported by tools that check publicly accessible plugins for access to deprecated (or to-be-deprecated) APIs and generate reports on them to inform deprecation policy decisions.Ideally, Jenkins core will be enhanced to include the capability to check both plugins for use of removed APIs, so it can refuse to load plugins considered incompatible with the running Jenkins version, and the update site generation should be improved to exclude plugins that are known incompatible with the core release downloading the plugin information.h1. ImpactThe impact of this change is not currently known both due to the large number of deprecated APIs and because we don't currently have the tooling above.Removal of APIs needs to be done carefully (rather than wholesale), and affected, open-source plugins hosted by the Jenkins project need to be fixed to no longer rely on those APIs. This will force users to update affected plugins when updating Jenkins itself (which may be inconvenient if the new plugin release not using deprecated APIs is not compatible with the previously installed version), but it should at least ensure continued operation of their plugins.This change may increase the frequency by which new plugin versions require newer core releases to run, as the replacement APIs may be new to the release that deprecated the existing API.h1. Open questions* How long is the deprecation period before an API gets removed?** Should the same duration be used for all deprecations, or should it depend on the specific API?*** If the latter, what are the lower/upper bounds, if any, of the deprecation period before removal?* What steps need to be followed to define a removal date for an API? Examples:*# Provide a list of affected plugins and propose how they can be fixed? (618 plugins are using a deprecated api among which a large number are only using Hudson.getInstance() or Plugin(), see [details here|https://ci.jenkins-ci.org/view/ Infrastructure All /job/ Reporting/job/ infra_deprecated-usage-in-plugins/lastSuccessfulBuild/artifact/target/output.html]. [~evernat])*# Provide a list of affected plugins and fix them (possibly including releases)?*# Public announcements of API removal?*# Documentation
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat edited a comment on JENKINS-31035 Re: Introduce a policy for API deprecation > Provide a list of affected plugins and propose how they can be fixed?There are at least 618 plugins using a deprecated Jenkins api, among which a large number are only using Hudson.getInstance() or Plugin().20 deprecated classes, 172 deprecated methods and 13 deprecated fields are used in plugins.28 deprecated and public Jenkins classes, 318 deprecated methods, 58 deprecated fields are not used in the latest published plugins (and which may be removed as part of Jenkins 2.0 ?).You can see details for each plugin and of used or not deprecated api at https://ci.jenkins-ci.org/view/ Infrastructure All /job/ Reporting/job/ infra_deprecated-usage-in-plugins/lastSuccessfulBuild/artifact/target/output.htmlPerhaps, some PR could be submitted to fix some of these plugins during [Jenkins Hacksgiving|https://wiki.jenkins-ci.org/display/JENKINS/Hacksgiving+2015] in the next few days ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-32377) Upgrade Jetty to fix bugs in cookies
Title: Message Title evernat assigned an issue to Unassigned Jenkins / JENKINS-32377 Upgrade Jetty to fix bugs in cookies Change By: evernat Assignee: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookies to be saved
Title: Message Title evernat commented on JENKINS-25917 Re: Spaces in URL (from project name or view) cause invalid cookies to be saved yes, cookie path is correct and http header "Set-Cookie" received by the browser seems also correct: Server Jetty(winstone-2.9) Set-Cookie TestResultAction_failureOnly=false;Path="/job/project%20with%20spaces";Expires=Mon, 09-Jan-2017 11:27:25 GMT But the cookie is not saved correctly by the browser (Chrome and Firefox), certainly because of quotes in the Path. It happens that Jenkins uses Jetty 8.1.13 (https://github.com/jenkinsci/winstone/blob/master/pom.xml#L221) which is buggy (see here and here) It will be needed to upgrade Jetty to 9.0.6 or later. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-32377) Upgrade Jetty to fix bugs in cookies
Title: Message Title evernat created an issue Jenkins / JENKINS-32377 Upgrade Jetty to fix bugs in cookies Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin, core, junit-plugin, winstone-jetty Created: 10/Jan/16 12:03 PM Priority: Major Reporter: evernat Jetty is causing bugs in junit and analysis graphs because of cookies for paths with whitespaces. See JENKINS-25917 Jenkins uses Jetty 8.1.13 (https://github.com/jenkinsci/winstone/blob/master/pom.xml#L221) which is buggy (see here and here) It is needed to upgrade Jetty to 9.0.6 or later. Add Comment
[JIRA] [core] (JENKINS-23063) White spaces in a Project name of a job makes the Test Result Trend fail
Title: Message Title evernat resolved as Duplicate Jenkins / JENKINS-23063 White spaces in a Project name of a job makes the Test Result Trend fail Change By: evernat Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23863) HTTP requests hang indefinitely after some time running
Title: Message Title evernat resolved as Not A Defect the server memory is full, it's normal that the server stops responding Jenkins / JENKINS-23863 HTTP requests hang indefinitely after some time running Change By: evernat Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23456) I'm getting 23456!!!
Title: Message Title evernat resolved as Incomplete Yes, you can. Jenkins / JENKINS-23456 I'm getting 23456!!! Change By: evernat Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-1350) hpi:run should use non-empty context path
Title: Message Title evernat resolved as Fixed hpi:run now uses a non-empty context path (/jenkins) Jenkins / JENKINS-1350 hpi:run should use non-empty context path Change By: evernat Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat updated an issue Jenkins / JENKINS-31035 Introduce a policy for API deprecation Change By: evernat h1. Problem definitionCurrently, we have no backward compatibility policy besides ["compatibility matters"|https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Compatibilitymatters]. With 1000+ plugins and basically the entire core being available to plugins, a lot of difficult or impossible to remove cruft has accumulated over the last ten years. This limits both what can be changed in core, and makes documentation difficult to use for plugin developers.Elaborate solutions such as the bytecode compatibility transformer currently (Oct 2015) introduce difficult to investigate bugs that result in things breaking for users.h1. ProposalLimit the availability in APIs (classes, methods, fields, …) provided by core to a number of releases. Depending on the feature, this can range from a few months, to a few years (e.g. two years being about 100 releases of Jenkins and eight LTS baselines).This deprecation policy needs to be supported by tools that check publicly accessible plugins for access to deprecated (or to-be-deprecated) APIs and generate reports on them to inform deprecation policy decisions.Ideally, Jenkins core will be enhanced to include the capability to check both plugins for use of removed APIs, so it can refuse to load plugins considered incompatible with the running Jenkins version, and the update site generation should be improved to exclude plugins that are known incompatible with the core release downloading the plugin information.h1. ImpactThe impact of this change is not currently known both due to the large number of deprecated APIs and because we don't currently have the tooling above.Removal of APIs needs to be done carefully (rather than wholesale), and affected, open-source plugins hosted by the Jenkins project need to be fixed to no longer rely on those APIs. This will force users to update affected plugins when updating Jenkins itself (which may be inconvenient if the new plugin release not using deprecated APIs is not compatible with the previously installed version), but it should at least ensure continued operation of their plugins.This change may increase the frequency by which new plugin versions require newer core releases to run, as the replacement APIs may be new to the release that deprecated the existing API.h1. Open questions* How long is the deprecation period before an API gets removed?** Should the same duration be used for all deprecations, or should it depend on the specific API?*** If the latter, what are the lower/upper bounds, if any, of the deprecation period before removal?* What steps need to be followed to define a removal date for an API? Examples:*# Provide a list of affected plugins and propose how they can be fixed? ( 435 618 plugins are using a deprecated api among which a large number are only using Hudson.getInstance() or Plugin() , see [details here|https:// github ci . com jenkins-ci.org / evernat view / deprecated Infrastructure/job/infra_deprecated -usage-in-plugins/ blob lastSuccessfulBuild / master artifact / Output_example target/output . txt html ]. [~evernat])*# Provide a list of affected plugins and fix them (possibly including
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat edited a comment on JENKINS-31035 Re: Introduce a policy for API deprecation > Provide a list of affected plugins and propose how they can be fixed?There are at least 435 618 plugins using a deprecated Jenkins api , among which a large number are only using Hudson . getInstance() or Plugin(). 19 20 deprecated classes, 166 172 deprecated methods and 12 13 deprecated fields are used in plugins. 29 28 deprecated and public Jenkins classes, 312 318 deprecated methods, 58 deprecated fields are not used in the latest published plugins (and which may be removed as part of Jenkins 2.0 ?).You can see details for each plugin and of used or not deprecated api at https:// github ci . com jenkins-ci.org / evernat view / deprecated Infrastructure/job/infra_deprecated -usage-in-plugins/ blob lastSuccessfulBuild / master artifact / Output_example.txt(I will suggest to run this tool automatically at https: target / /ci output . jenkins-ci.org/ or https://jenkins.ci.cloudbees.com/) html Perhaps, some PR could be submitted to fix some of these plugins during [Jenkins Hacksgiving|https://wiki.jenkins-ci.org/display/JENKINS/Hacksgiving+2015] in the next few days ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vmware-vrealize-automation-plugin] (JENKINS-32261) Exclude bcprov dependencies
Title: Message Title evernat created an issue Jenkins / JENKINS-32261 Exclude bcprov dependencies Issue Type: Improvement Assignee: Kris Thieler Components: vmware-vrealize-automation-plugin Created: 31/Dec/15 4:15 PM Priority: Major Reporter: evernat vmware-vrealize-automation-plugin.hpi v1.0.1 contains bcmail-jdk16-1.46.jar, bcprov-jdk15on-1.53.jar and bcprov-jdk16-1.46.jar But Jenkins already contains bcprov-jdk15on-1.47.jar. I suggest to exclude bcprov-jdk15on-1.53.jar and bcprov-jdk16-1.46.jar from the dependencies of the plugin in order to avoid conflicts in Jenkins and other plugins. Add Comment
[JIRA] [monitoring-plugin] (JENKINS-20798) User column of http session is empty without login
Title: Message Title evernat assigned an issue to evernat Jenkins / JENKINS-20798 User column of http session is empty without login Change By: evernat Assignee: evernat Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-31619) java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N
Title: Message Title evernat resolved as Cannot Reproduce I do not have this issue. I suggest to restart the server and see if reproduced. Jenkins / JENKINS-31619 java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N Change By: evernat Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-20798) User column of http session is empty without login
Title: Message Title evernat resolved as Fixed Should be fixed by https://github.com/jenkinsci/monitoring-plugin/commit/d261b03f7762e903724599fbf84eaa3a2d48 It will be in the next release (1.59) in a few months. You can download a nightly build at: https://jenkins.ci.cloudbees.com/job/plugins/job/monitoring-plugin/ws/target/monitoring.hpi Jenkins / JENKINS-20798 User column of http session is empty without login Change By: evernat Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-14130) reloading http://host/monitoring several times fast give exception
Title: Message Title evernat resolved as Won't Do No response from the reporter. Closing as invalid. Jenkins / JENKINS-14130 reloading http://host/monitoring several times fast give exception Change By: evernat Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat commented on JENKINS-31035 Re: Introduce a policy for API deprecation Daniel Beck, the python-wrapper plugin is now ignored. In fact, the job is currently scheduled hourly not daily. And you may discard old builds of the job. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat commented on JENKINS-31035 Re: Introduce a policy for API deprecation Yes, no problem. You can fork it to jenkinsci/ My github id is evernat so that I can push to the repo. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat commented on JENKINS-31035 Re: Introduce a policy for API deprecation Daniel Spilker, I have created this issue for you with an answer. In short, for (Cloud cloud : jenkins.clouds will not be displayed as using a deprecated api anymore. And I have added a list of deprecated api by plugins. Daniel Beck, can you schedule the job periodically or at least run it once. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat commented on JENKINS-31035 Re: Introduce a policy for API deprecation Daniel Spilker I suggest that you create an issue at https://github.com/evernat/deprecated-usage-in-plugins/issues to continue the discussion and not in this page. (The answer could be yes and no, it depends on the point of view on source or on class.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat commented on JENKINS-31035 Re: Introduce a policy for API deprecation > Provide a list of affected plugins and propose how they can be fixed? There are at least 435 plugins using a deprecated Jenkins api. 19 deprecated classes, 166 deprecated methods and 12 deprecated fields are used in plugins. 29 deprecated and public Jenkins classes, 312 deprecated methods, 58 deprecated fields are not used in the latest published plugins (and which may be removed as part of Jenkins 2.0 ?). You can see details for each plugin and of used or not deprecated api at https://github.com/evernat/deprecated-usage-in-plugins/blob/master/Output_example.txt (I will suggest to run this tool automatically at https://ci.jenkins-ci.org/ or https://jenkins.ci.cloudbees.com/) Perhaps, some PR could be submitted to fix some of these plugins during Jenkins Hacksgiving in the next few days ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31035) Introduce a policy for API deprecation
Title: Message Title evernat updated an issue Jenkins / JENKINS-31035 Introduce a policy for API deprecation Change By: evernat h1. Problem definitionCurrently, we have no backward compatibility policy besides ["compatibility matters"|https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Compatibilitymatters]. With 1000+ plugins and basically the entire core being available to plugins, a lot of difficult or impossible to remove cruft has accumulated over the last ten years. This limits both what can be changed in core, and makes documentation difficult to use for plugin developers.Elaborate solutions such as the bytecode compatibility transformer currently (Oct 2015) introduce difficult to investigate bugs that result in things breaking for users.h1. ProposalLimit the availability in APIs (classes, methods, fields, …) provided by core to a number of releases. Depending on the feature, this can range from a few months, to a few years (e.g. two years being about 100 releases of Jenkins and eight LTS baselines).This deprecation policy needs to be supported by tools that check publicly accessible plugins for access to deprecated (or to-be-deprecated) APIs and generate reports on them to inform deprecation policy decisions.Ideally, Jenkins core will be enhanced to include the capability to check both plugins for use of removed APIs, so it can refuse to load plugins considered incompatible with the running Jenkins version, and the update site generation should be improved to exclude plugins that are known incompatible with the core release downloading the plugin information.h1. ImpactThe impact of this change is not currently known both due to the large number of deprecated APIs and because we don't currently have the tooling above.Removal of APIs needs to be done carefully (rather than wholesale), and affected, open-source plugins hosted by the Jenkins project need to be fixed to no longer rely on those APIs. This will force users to update affected plugins when updating Jenkins itself (which may be inconvenient if the new plugin release not using deprecated APIs is not compatible with the previously installed version), but it should at least ensure continued operation of their plugins.This change may increase the frequency by which new plugin versions require newer core releases to run, as the replacement APIs may be new to the release that deprecated the existing API.h1. Open questions* How long is the deprecation period before an API gets removed?** Should the same duration be used for all deprecations, or should it depend on the specific API?*** If the latter, what are the lower/upper bounds, if any, of the deprecation period before removal?* What steps need to be followed to define a removal date for an API? Examples:*# Provide a list of affected plugins and propose how they can be fixed? (435 plugins are using a deprecated api, see [details here|https://github.com/evernat/deprecated-usage-in-plugins/blob/master/Output_example.txt]. [~evernat]) *# Provide a list of affected plugins and fix them (possibly including releases)?*# Public announcements of API removal?*# Documentation (Javadoc) updates?*# Add an annotation to the removed element to allow automated processing?* Who fixes the plugins?** Have a team responsible
[JIRA] [monitoring-plugin] (JENKINS-31383) HTTP session count leak
Title: Message Title evernat commented on JENKINS-31383 Re: HTTP session count leak First, please upgrade to the latest version (1.57.0) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-31383) HTTP session count leak
Title: Message Title evernat resolved as Won't Do Jenkins / JENKINS-31383 HTTP session count leak Change By: evernat Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-31383) HTTP session count leak
Title: Message Title evernat closed an issue as Won't Do Jenkins / JENKINS-31383 HTTP session count leak Change By: evernat Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Title: Message Title evernat commented on JENKINS-23442 Re: Jenkins 1.568 can not start when monitoring plugin is installed Thanks Anders for the confirmation. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Title: Message Title evernat resolved as Fixed Jenkins / JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Change By: evernat Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Title: Message Title evernat commented on JENKINS-23442 Re: Jenkins 1.568 can not start when monitoring plugin is installed The code changed in the plugin is a tentative fix without having reproduced the issue myself. So, I would like a confirmation from a user before saying that it is fixed. To everyone: You can test the fix by downloading a nightly build here: https://javamelody.ci.cloudbees.com/job/jenkins%20plugin/ws/target/monitoring.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29971) Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d
Title: Message Title evernat updated an issue Jenkins / JENKINS-29971 Failed to load index from org.kohsuke.stapler.jelly.groovy.GroovyFacet@2cc7b16d org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter is in the stack-trace like in the stack-traces of many http requests. But this is not related to the monitoring plugin. Change By: evernat Component/s: core Component/s: monitoring-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Title: Message Title evernat commented on JENKINS-23442 Re: Jenkins 1.568 can not start when monitoring plugin is installed After reading JENKINS-27669 , perhaps it is needed to preload the java.util.logging.LogRecord class, before net.bull.javamelody.LoggingHandler.publish(...) is called. @Jens Brejner A possible cause triggering the issue for you may be that you have also the "Logging plugin" installed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [simple-parameterized-builds-report-plugin] (JENKINS-30264) Merge code to jenkinsci
Title: Message Title evernat created an issue Jenkins / JENKINS-30264 Merge code to jenkinsci Issue Type: Task Assignee: Unassigned Components: simple-parameterized-builds-report-plugin Created: 02/Sep/15 11:40 AM Priority: Minor Reporter: evernat In the wiki page, the github links go to https://github.com/jenkinsci/simple-parameterized-builds-report-plugin But this repo does not contain the latest source and is one year late. The latest source is not easy to find. Please merge the latest changes in https://github.com/jenkinsci/simple-parameterized-builds-report-plugin so that everyone can: check license issues, check security issues, fix bugs and enhance the plugin... By the way, what is the license of the plugin? MIT like many other plugins? It would be better to add a license in pom.xml and in a LICENSE file. https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites
[JIRA] [simple-parameterized-builds-report-plugin] (JENKINS-30264) Merge code to jenkinsci
Title: Message Title evernat assigned an issue to Nalin Makar Jenkins / JENKINS-30264 Merge code to jenkinsci Change By: evernat Assignee: Nalin Makar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Title: Message Title evernat updated an issue Jenkins / JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed As said above, the monitoring plugin currently bundles the slf4j-api. Can you try a new build of the monitoring plugin without the slf4j-api? monitoring.hpi is attached and is the same as v1.56 except slf4j-api. You can install it in your Jenkins with Manage Jenkins / Manage plugins / Advanced / Upload plugin. Change By: evernat Attachment: monitoring.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-29489) Fix How to use in the wiki
Title: Message Title evernat updated an issue Jenkins / JENKINS-29489 Fix How to use in the wiki Change By: evernat Inthe[wikipage|https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin],the[Howtouse|https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin#FindBugsPlugin-HowToUse]says:plugingroupIdorg.codehaus.mojo/groupIdartifactIdfindbugs-maven-plugin/artifactIdversion2.5.2/versionconfigurationfindbugsXmlOutputtrue/findbugsXmlOutputfindbugsXmlWithMessagestrue/findbugsXmlWithMessagesxmlOutputtrue/xmlOutput/configuration/pluginButitseemstomethatfindbugsXmlWithMessagesdoesnotexistanymoreandshouldberemovedfromthehowto.And from the helpfilestoo:https://github.com/jenkinsci/findbugs-plugin/tree/master/plugin/src/main/webappAndthe versionofthefindbugs-maven-plugincouldbeupgraded inthehowtoandinthehelpfiles . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-29489) Fix How to use in the wiki
Title: Message Title evernat updated an issue Jenkins / JENKINS-29489 Fix How to use in the wiki Change By: evernat URL: https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin #FindBugsPlugin-HowToUse Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-29489) Fix How to use in the wiki
Title: Message Title evernat created an issue Jenkins / JENKINS-29489 Fix How to use in the wiki Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 19/Jul/15 9:15 AM Priority: Minor Reporter: evernat In the wiki page, the How to use says: plugin groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.5.2/version configuration findbugsXmlOutputtrue/findbugsXmlOutput findbugsXmlWithMessagestrue/findbugsXmlWithMessages xmlOutputtrue/xmlOutput /configuration /plugin But it seems to me that findbugsXmlWithMessages does not exist anymore and should be removed from the how to. And the version of the findbugs-maven-plugin could be upgraded. Add Comment
[JIRA] [findbugs-plugin] (JENKINS-29489) Fix How to use in the wiki
Title: Message Title evernat updated an issue Jenkins / JENKINS-29489 Fix How to use in the wiki Change By: evernat Inthe[wikipage|https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin],the[Howtouse|https://wiki.jenkins-ci.org/display/JENKINS/FindBugs+Plugin#FindBugsPlugin-HowToUse]says:plugingroupIdorg.codehaus.mojo/groupIdartifactIdfindbugs-maven-plugin/artifactIdversion2.5.2/versionconfigurationfindbugsXmlOutputtrue/findbugsXmlOutputfindbugsXmlWithMessagestrue/findbugsXmlWithMessagesxmlOutputtrue/xmlOutput/configuration/pluginButitseemstomethatfindbugsXmlWithMessagesdoesnotexistanymoreandshouldberemovedfromthehowto.Andfromthehelpfilestoo:https://github.com/jenkinsci/findbugs-plugin/tree/master/plugin/src/main/webappAndtheversionofthefindbugs-maven-plugincouldbeupgradedinthehowtoandinthehelpfiles (to3 . 0.0andnot3.0.1forFrenchpeople). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-28325) Latest source of the plugin not in github repo
Title: Message Title evernat created an issue Jenkins / JENKINS-28325 Latest source of the plugin not in github repo Issue Type: Task Assignee: Praqma Support Components: config-rotator-plugin Created: 10/May/15 2:56 PM Priority: Major Reporter: evernat The wiki page gives links to the github repo with the sources. But the sources are not up to date with the latest changes and releases: it contains 1.1.8-SNAPSHOT but 1.1.9 was released on January 29. And it's difficult to know where are the latest sources. I suggest to merge your latest sources in the github repo, so that everyone can check: if it is closed-source or open-source, if there are license issues, if there are security issues, if there are bugs in the code which can be fixed. Thanks
[JIRA] [jenkins-jira-issue-updater] (JENKINS-28229) plugin-info markup generates incorrect Open Issues link
Title: Message Title evernat commented on JENKINS-28229 Re: plugin-info markup generates incorrect Open Issues link Yes there is a convention for component names in Jira since the project meeting of Nov 12th 2014. So I have created issue INFRA-299 in the infrastructure projet in order that the jira component is renamed to jenkins-jira-issue-updater-plugin. When the INFRA-299 is done and if the new name is exactly jenkins-jira-issue-updater-plugin, the Open issues link in the wiki page will work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
evernat commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Without preventing you to give info, it can be noted that the monitoring plugin currently bundles the slf4j-api: https://github.com/jenkinsci/monitoring-plugin/blob/master/pom.xml#L49 Sl4j-api is in theory not related to java.util.logging, but I can build a specific version without that if you want to make a test. (Or you can remove WEB-INF/lib/slf4j-api-1.6.3.jar by yourself from the monitoring.hpi file with a zip manager and then uninstall / reinstall.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27429) Links to archives and to download section are 404 for the Warnings plugin
evernat created JENKINS-27429 Links to archives and to download section are 404 for the Warnings plugin Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 14/Mar/15 10:45 PM Description: In https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin the plugin info gives an "archives" link: http://updates.jenkins-ci.org/download/plugins/warnings/ and below in the page there is also a "download section" link: http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/plugins/warnings/ Both links are invalid for years. Do you know why? This is related to INFRA-221 Project: Jenkins Priority: Minor Reporter: evernat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-24838) Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context
evernat resolved JENKINS-24838 as Incomplete Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context No response from the reporter, so resolving as incomplete. Please reopen if you have information to reproduce. Change By: evernat (05/Jan/15 7:11 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-15736) Viewing performance report changes jvm locale
evernat updated JENKINS-15736 Viewing performance report changes jvm locale Change By: evernat (30/Dec/14 12:42 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-15736) Viewing performance report changes jvm locale
evernat
commented on JENKINS-15736
Viewing performance report changes jvm locale
In my opinion, this issue is critical since it affects all Jenkins core and installed plugins.
Based on the code, there is at least one line in the plugin which causes this issue and it is easy to fix:
https://github.com/jenkinsci/performance-plugin/blob/master/src/main/java/hudson/plugins/performance/AbstractReport.java#L21
In fact, the method Locale.setDefault(...) must never be called by the plugin.
I suggest to change the constructor of AbstractReport from
public AbstractReport() {
if (Stapler.getCurrentRequest() != null) {
Locale.setDefault(Stapler.getCurrentRequest().getLocale());
}
percentFormat = new DecimalFormat("0.0");
dataFormat = new DecimalFormat("#,###");
}
to
public AbstractReport() {
final Locale locale;
if (Stapler.getCurrentRequest() != null) {
locale = Stapler.getCurrentRequest().getLocale();
} else {
locale = Locale.getDefault();
}
percentFormat = new DecimalFormat("0.0", DecimalFormatSymbols.getInstance(locale));
dataFormat = new DecimalFormat("#,###", DecimalFormatSymbols.getInstance(locale));
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring-plugin] (JENKINS-24838) Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context
evernat commented on JENKINS-24838 Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context Any news? Note that I have not reproduced the issue (monitoring plugin v1.53.0, Jenkins v1.585). So if you don't give more information as asked in the comment above, this can't be fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25795) The Test drive in the Meet Jenkins wiki page needs a link
evernat created JENKINS-25795 The Test drive in the Meet Jenkins wiki page needs a link Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/14 11:44 AM Description: A http link should be added on the "Launch Jenkins" words to http://jenkins-ci.org/jenkins.jnlp in the "Test drive" of the "Meet Jenkins" wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins#MeetJenkins-TestDrive Without that link, that "Test drive" goes nowhere. Note that the link was present some time ago. And http://jenkins-ci.org/jenkins.jnlp works now in JavaWebStart (it was fixed by JENKINS-14924). The "Meet Jenkins" page is locked so a wiki admin is needed. Project: Jenkins Priority: Major Reporter: evernat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/d/optout.
