|
||||||||
|
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/groups/opt_out.
this issue has driven me completely mad for months, and I just identified tonight that it is in fact two different "classes" of console output, based on the size of the log, and then from that "class" you get two entirely different UX treatments - the presence or lack of a "breadcrumb" link to the console output (why is the contextual popup called a "breadcrumb?" not really a breadcrumb...), as well as either "console output ... view as plain text" on the right for small logs or "console output [raw]" for large logs when you view the build itself.
evernat seems to have identified this size as 200K, sounds about right - why isn't this hardcoded number configurable or documented anywhere ? why two entirely different sets of logic kicking in? why can't jenkins pay for all the psychiatric meds this issue has caused me? so many questions.... thanks for listening.