My first thought was that log annotators could have an issue with this if they are wrongly assuming being fed one line at the time. But they might be handled separate from this?
Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications > -----Original Message----- > From: [email protected] [mailto:jenkinsci- > [email protected]] On Behalf Of Jesse Glick > Sent: den 27 juli 2013 00:33 > To: [email protected] > Subject: Re: progressiveHtml url/doProgressText() only shows a line at > a time > > On Fri, Jul 26, 2013 at 6:26 PM, Haszlakiewicz, Eric > <[email protected]> wrote: > > I don't think you'd want to inject an extra one second delay into > every request. > > Nor was I suggesting that. My suggestion was that if the last character > in the log file at the time of the request was not a newline, then the > partial line would be sent to the client iff the last newline was > encountered at least one second before the current request. > > For regular jobs, which do not use "cooked-mode" progress bars, there > would be no change in behavior at all. For jobs with progress bars, you > would see the bar move, with merely a second lag time. > > -- > 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. > -- 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.
