<https://lh5.googleusercontent.com/-7PvxRwbwFzA/USeCQNiVg3I/AAAAAAAAABY/dmaXHkw_AO8/s1600/jenkins_log2.png>
Hi Jesse,
Thanks for the tip! My logger name was
"org.jenkinsci.plugins.helloworld.HelloWorldBuilder". When I changed it
to, "jenkins.HelloWorldBuilder" the warning was logged to the Jenkins Log.
------------------
...
private static final Logger LOGGER =
Logger.getLogger("jenkins.HelloWorldBuilder"); // NEW LINE
...
------------------
I supposed this means when a plugin experiences an unexpected error and
logs it as SEVERE, the admin would have to add a logger and reproduce the
problem to get the stack trace. The admin would probably have to go to our
plugin's wiki page to find the plugin's namespace to know what to log.
Then the admin could report an issue with the plugin. My concern with this
approach is that it encourages us to log the stack trace right in the job's
console or return a form validation error with a stack trace to the web UI
during validation so the user has enough information to report a problem
right away.
Is the the intended approach? How have users been reporting plugin issues
traditionally? Do they supply a stack trace?
Thanks again for your help,
Scott
On Thursday, February 21, 2013 5:31:35 PM UTC-5, Jesse Glick wrote:
>
> On 02/21/2013 04:28 PM, Scott Cowan wrote:
> > The warning is written to the console, but not the Jenkins Log. Is this
> a defect?
>
> According to WebAppMain.installLogger, only loggers in the hudson.* or
> jenkins.* namespaces are kept, so check your logger name.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
