Merge lp:~pfalcon/linaro-android-frontend/more-logs into lp:linaro-android-frontend

[Paul Sokolovsky]

Raw, big, unwrapped build log linked currently from frontend is hardly the best choice - actually, it's suitable only for downloading, not online browsing. On the other hand, default Jenkins log is pretty useful, and some time ago we added Log Parser's parsed log. So, show links to all 3.

[Michael Hudson-Doyle (mwhudson)]

Seems fine.

I have a branch that adds live console output to the build page but there's no way to find out how large a build log is without downloading all of it :(

review: Approve

[Paul Sokolovsky (pfalcon)]

On Tue, 25 Oct 2011 22:36:23 -0000
Michael Hudson-Doyle <email address hidden> wrote:

> Review: Approve
>
> Seems fine.
>
> I have a branch that adds live console output to the build page but
> there's no way to find out how large a build log is without
> downloading all of it :(

Yep, I remember you told about this. I also wonder if it's scalable to
try do duplicate all Jenkins features in frontend. We're using more and
more its features, and I hope we're past indecisiveness stage regarding
Jenkins, so hopefully we don't want to "hide" it with frontend, just
use fronted as a simplified "dashboard" instead, forwarding users
directly to Jenkins for more advanced info...

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

[Michael Hudson-Doyle (mwhudson)]

On Wed, 26 Oct 2011 15:37:29 -0000, Paul Sokolovsky <email address hidden> wrote:
> On Tue, 25 Oct 2011 22:36:23 -0000
> Michael Hudson-Doyle <email address hidden> wrote:
>
> > Review: Approve
> >
> > Seems fine.
> >
> > I have a branch that adds live console output to the build page but
> > there's no way to find out how large a build log is without
> > downloading all of it :(
>
> Yep, I remember you told about this. I also wonder if it's scalable to
> try do duplicate all Jenkins features in frontend. We're using more and
> more its features, and I hope we're past indecisiveness stage regarding
> Jenkins, so hopefully we don't want to "hide" it with frontend, just
> use fronted as a simplified "dashboard" instead, forwarding users
> directly to Jenkins for more advanced info...

Yeah, that's also a fair point.

Cheers,
mwh

=== modified file 'static/buildDetails.js'
--- static/buildDetails.js	2011-10-21 04:04:22 +0000
+++ static/buildDetails.js	2011-10-25 19:06:25 +0000
@@ -140,8 +140,8 @@
         }
       },
       loglink: function (results) {
-        return Y.Node.create('<a>complete output</a>').setAttribute(
-          'href', results.buildUrl + '/consoleText');
+        return '<a href="' + results.buildUrl + '/parsed_console">Parsed</a> - <a href="' 
+              + results.buildUrl + '/console">Tail</a> - <a href="' + results.buildUrl + '/consoleText">Raw</a>';
       },
       testresults: function (results) {
           if (results.artifacts.length) {