[JIRA] (JENKINS-39521) Full Log should not be served as plain text
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39521 Full Log should not be served as plain text Change By: James Dumay Assignee: Thorsten Scherler 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-39521) Full Log should not be served as plain text
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39521 Full Log should not be served as plain text Change By: James Dumay Issue Type: Bug Improvement 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-39521) Full Log should not be served as plain text
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39521 Full Log should not be served as plain text Change By: James Dumay Summary: Full log Log should not using correct whitespace be served as plain text 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-39521) Full Log should not be served as plain text
Title: Message Title Samuel Reed commented on JENKINS-39521 Re: Full Log should not be served as plain text Yep that's the one, but it actually is served as HTML (perhaps the plugins are doing it?). Connection:keep-alive Content-Encoding:gzip Content-Length:20104 Content-Type:text/html;charset=UTF-8 Date:Mon, 07 Nov 2016 00:58:50 GMT Server:nginx/1.4.6 (Ubuntu) X-Text-Size:675129 It's basically text with anchor tags, no or , etc. 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-39521) Full Log should not be served as plain text
Title: Message Title James Dumay commented on JENKINS-39521 Re: Full Log should not be served as plain text Samuel Reed I don't think we can serve this one up in HTML like you've asked for in this ticket. Unbounded log file rendered with some CSS will likely hang your browser. Quick question, what is taking you back to the full log? 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-39521) Full Log should not be served as plain text
Title: Message Title Samuel Reed commented on JENKINS-39521 Re: Full Log should not be served as plain text It's already HTML. I'm not sure what's automatically creating the anchors, but it's not AnsiColor (verified by removing it). So that's more or less a sunk cost. Alternatively, if it were formatted as plain text with no formatting whatsoever, it might render more quickly. It would have to be a huge build for it to matter.. The full log is the link from the pipeline. There's an example in the original description. 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-39521) Full Log should not be served as plain text
Title: Message Title James Dumay commented on JENKINS-39521 Re: Full Log should not be served as plain text Samuel Reed being the Jenkins project we have to take into account those huge builds I think we certainly need to send the right content type here. 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-39521) Full Log should not be served as plain text
Title: Message Title Thorsten Scherler commented on JENKINS-39521 Re: Full Log should not be served as plain text James Dumay the full log is coming from jenkins directly bo is not directly serving this. AFAIR Vivek Pandey implemented that. 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-39521) Full Log should not be served as plain text
Title: Message Title James Dumay commented on JENKINS-39521 Re: Full Log should not be served as plain text Samuel Reed I am told it operates purely on the Accept header. I don't think the browser is doing much work in this case and we haven't had any performance reports. 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-39521) Full Log should not be served as plain text
Title: Message Title James Dumay resolved as Not A Defect Closing this out as Not A Defect. If there is any reason to open this ticket again please do so. Jenkins / JENKINS-39521 Full Log should not be served as plain text Change By: James Dumay Status: Open Resolved Resolution: Not A Defect 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 mor
[JIRA] (JENKINS-39521) Full Log should not be served as plain text
Title: Message Title Samuel Reed commented on JENKINS-39521 Re: Full Log should not be served as plain text Excuse my incredulity, but you are saying that it is "Not A Defect" that logfiles as served by Jenkins/BO don't respect newline characters? So logs looking like is just fine? 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-39521) Full Log should not be served as plain text
Title: Message Title Samuel Reed reopened an issue Jenkins / JENKINS-39521 Full Log should not be served as plain text Change By: Samuel Reed Resolution: Not A Defect Status: Resolved Reopened 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.
