-
Bug
-
Resolution: Fixed
-
Major
-
2.28, 915bc21
-
-
iapetus
Scope
- Force text/plain content type on full log endpoint
Original Request
When displaying the full log for a step, e.g. at https://jenkins.my-domain.com/blue/rest/organizations/jenkins/pipelines/Org/project/branches/master/runs/90/log/?start=0, the log is rendered as HTML with colors, anchors, etc., but line breaks are not renders as <br />.
That's fine to do, but if so, the body should have a `style="white-space: pre-wrap"` or you end up with an enormous wall of unbroken text.
[JENKINS-39521] Full Log does not render newlines - or use correct content type (weird HTML like artifacts)
teilo thanks we've seen this too. We are going to look at it in the next sprint 
if it is shown as HTML - will it behave correctly or will console annotators mess with it? If so - best to show plain text and probably show the classic console view for those that want to use annotators for now?
EDIT: oh that plain wrapped like strml suggested could be good to - worth a try.
Got same problem, unable to read logs as a result ) looks like at least Firefox treats full log as HTML code and renders a mess
jamesdumay is this the right place to just report that "show full logs" button opens the tab with logs that are being rendered as HTML in Firefox ?
kamikaze that one has been fixed in master and will be out in next release.
michaelneale I have latest BlueOcean 1.0.0-b23 . Logs are still being rendered as a one line text that takes the whole screen. At least in Firefox
jamesdumay this is reproduceable internally - ping me if you want more details.