Cruisecontrolrb users - May 2008 - version 1.3 build log truncation

Hi All,
I have upgraded to verion 1.3. Our build output has huge
text in it and what I notice is that in 1.3 the I do not
see complete build.log.

Is there any flag to control this? I want to see the complete
build output because the last few lines has interesting output
about what part of build failed.

Thanks and Regard,
Manish

Hi All,
I have upgraded to verion 1.3. Our build output has huge
text in it and what I notice is that in 1.3 the I do not
see complete build.log.

Is there any flag to control this? I want to see the complete
build output because the last few lines has interesting output
about what part of build failed.

Thanks and Regard,
Manish

Is the truncation in the build log file itself or just in the on-screen
rendering?

On Sun, May 25, 2008 at 2:32 AM, Manish Sapariya <manish at gslab.com>
wrote:
> Our build output has huge
> text in it and what I notice is that in 1.3 the I do not
> see complete build.log.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080525/18432f70/attachment.html>

On Sun, May 25, 2008 at 7:53 AM, John D. Hume <duelin.markers at
gmail.com> wrote:
> Is the truncation in the build log file itself or just in the on-screen
> rendering?
Pretty sure it''s just the web ui.  I believe you can even click the
link at the bottom of the build page to see the full log?

Hi,
its in webui when I click the build log, thats when it shows the
partial logs. With 1.2 it shows the complete build log file when I
click build log on GUI. I have not calculated but if looks like there
is some size limitation on how much data from file to show, but I am
clueless as what causes that.

Please let me know if I can provide more info.
Thanks and Regards,
Manish

Chad Woolley wrote:
> On Sun, May 25, 2008 at 7:53 AM, John D. Hume <duelin.markers at
gmail.com> wrote:
>> Is the truncation in the build log file itself or just in the on-screen
>> rendering?
> 
> Pretty sure it''s just the web ui.  I believe you can even click
the
> link at the bottom of the build page to see the full log?
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>

okay, so contents_for_display in build.rb is what you want to look at, it
currently looks like this :

  def contents_for_display(file)
    return '''' unless File.file?(file) &&
File.readable?(file)
    if File.size(file) < 100 * 1024
      File.read(file)
    else
      contents = File.read(file, 100 * 1024)
      "#{file} is over 100 kbytes - too big to display in the dashboard,
output is truncated\n\n\n#{contents}"
    end
  end

and I believe alexey added this code to protect against insanely long build
logs that could bring down the system.  what I would do is monkey patch
Build by doing something like this

class Build
  def contents_for_display(file)
    ...
  end
end

somewhere either in your site_config.rb file or if you only have one
project, even in your cruise_config.rb file.

I think we have the right behavior in the general case, but you have a
special case, and it''s appropriate for you to customize the product to
your
needs.

Jeremy

On Sun, May 25, 2008 at 8:59 PM, Manish Sapariya <manish at gslab.com>
wrote:
> Hi,
> its in webui when I click the build log, thats when it shows the
> partial logs. With 1.2 it shows the complete build log file when I
> click build log on GUI. I have not calculated but if looks like there
> is some size limitation on how much data from file to show, but I am
> clueless as what causes that.
>
> Please let me know if I can provide more info.
> Thanks and Regards,
> Manish
>
>
> Chad Woolley wrote:
>
>> On Sun, May 25, 2008 at 7:53 AM, John D. Hume <duelin.markers at
gmail.com>
>> wrote:
>>
>>> Is the truncation in the build log file itself or just in the
on-screen
>>> rendering?
>>>
>>
>> Pretty sure it''s just the web ui.  I believe you can even
click the
>> link at the bottom of the build page to see the full log?
>> _______________________________________________
>> Cruisecontrolrb-users mailing list
>> Cruisecontrolrb-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>>
>>  _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080526/d465da50/attachment.html>

On Mon, May 26, 2008 at 1:02 AM, Jeremy Stell-Smith
<jeremystellsmith at gmail.com> wrote:
> and I believe alexey added this code to protect against insanely long build
> logs that could bring down the system.  what I would do is monkey patch
Seems like this should be exposed in the config file?  "insanely long"
is probably dependent on your environment...

-- Chad

-----cruisecontrolrb-users-bounces at rubyforge.org wrote:
-----
>> Is the truncation in the build log file itself or just in the on-screen
>> rendering?
>Pretty sure it''s just the web ui.  I believe you can even click the
>link at the bottom of the build page to see the full log?
It is just in the UI. Rationale for this was provided by a situation where
several thousand tests were failing for the same reason, producing a huge
log file, and the dashboard was running out of memory trying to parse it.

The link at the bottom is not there yet, but surely is a good idea. I would
actually put it inside the message that says that the file was too long. It
would be even nicer if we displayed the first 100 Kb of the file, and had a
"See more" link at the end, that would serve the whole thing as a text
file, without parsing.

Send patches! :)

--Alex

+1

On Wed, May 28, 2008 at 9:05 AM, Alexey Verkhovsky <
averkhov at thoughtworks.com> wrote:
> -----cruisecontrolrb-users-bounces at rubyforge.org wrote: -----
> >> Is the truncation in the build log file itself or just in the
on-screen
> >> rendering?
> >Pretty sure it''s just the web ui.  I believe you can even
click the
> >link at the bottom of the build page to see the full log?
>
> It is just in the UI. Rationale for this was provided by a situation where
> several thousand tests were failing for the same reason, producing a huge
> log file, and the dashboard was running out of memory trying to parse it.
>
> The link at the bottom is not there yet, but surely is a good idea. I would
> actually put it inside the message that says that the file was too long. It
> would be even nicer if we displayed the first 100 Kb of the file, and had a
> "See more" link at the end, that would serve the whole thing as a
text
> file, without parsing.
>
> Send patches! :)
>
> --Alex
>
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080528/94eae25b/attachment.html>