You provide no reasons why this would be an improvement. Here are some why it wouldn't be:
1. Will be a regression for everyone parsing console output and assuming a line starts with the actual output. 2. I already have to download logs to view them in a editor all the time because the browser cannot handle any logs above ~25M or so. Making the sidepanel a minefield for blowing up my browser seems like a bad idea. And most of the time, the last few lines are sufficient anyway to determine what is going on. You might be able to make this work for you by setting the System property hudson.consoleTailKB to a ridiculously large value. On 31.07.2014, at 15:51, Andrew Gray <[email protected]> wrote: > Hi All, > > I have two proposals: > > 1. Include the LineNumbers plugin in the Jenkins core and make that the > default behaviour for the console log screen? > > 2. Make the Console link in the sidebar menu and the progress bar under a > running build navigate to: > > http://localhost:8080/job/<jobName>/<buildNumber>/consoleFull > > rather than the current: > > http://localhost:8080/job/TimesGuide/86/console > > For your consideration. > > Regards, > > Andrew > > -- > 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/d/optout. -- 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/d/optout.
