Replace gubernator links with spyglass links

[Katharine]

We want to deprecate gubernator (except for its PR dashboard). Before we can do that, we need to:

• Merge the PR history view (add pr history dashboard to Deck #10169)
• Show pod logs as necessary even when given GCS URLs
• Add testgrid integration (but do we really want to couple prow and testgrid? gubernator does this by reading the testgrid config proto...)
• Add links to view artifacts
• Improve the failed test display (at least make the failure text more legible)
• [ ] Node log viewing?
• For transitional purposes, add a link to gubernator

Anything I missed? We can already:

• Show the build log
• Show test results
• Show build metadata
• Show job histories

Some of these things are probably uncommon (node logs?) and at least initially are sufficiently served by the link to gubernator.

[Katharine]

/area prow/deck
/area gubernator
/assign

[spiffxp]

Add testgrid integration (but do we really want to couple prow and testgrid? gubernator does this by reading the testgrid config proto...)

The current coupling may be ugly, there's probably a better way to do it that will require some rearchitecting, but the mapping from job <-> history of job runs (in testgrid form) is very useful. I can quickly jump from how is this run doing, to how have all runs been doing

Improve the failed test display (at least make the failure text more legible)

Agree. I'm not sure how many people use the "click to see stdout/stderr" link, but if nothing else it's additional info captured in the junit file that could be displayed nicely

eg: https://gubernator.k8s.io/build/kubernetes-jenkins/logs/ci-kubernetes-node-kubelet/17584#k8sio-summary-api-nodeconformance-when-querying-statssummary-should-report-resource-usage-through-the-stats-api

[spiffxp]

From my design nerd perspective, it doesn't appear dense enough. Don't get me wrong, whitespace is good. This doesn't feel like it's been put through a pass with that kind of eye though.

Text is small. I see N different kinds of font styles. It would be nice use a grid or something for consistent alignment

[BenTheElder]

Yes... spyglass has basically no CSS yet because that comes after the functionality works fully! give me working podlogs cough @ibzib cough and I might take a look slash poke @Katharine

…

On Fri, Dec 7, 2018 at 11:09 AM Aaron Crickenberger < ***@***.***> wrote: From my design nerd perspective, it doesn't appear dense enough. Don't get me wrong, whitespace is good. This doesn't feel like it's been put through a pass with that kind of eye though. Text is small. I see N different kinds of font styles. It would be nice use a grid or something for consistent alignment [image: screen shot 2018-12-07 at 11 08 00 am] <https://user-images.githubusercontent.com/49258/49667589-683c4080-fa10-11e8-8184-b4c89cf37fdc.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#10375 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA4BqwLZBfVzt_J29Jm9SoBtFm3o9EU8ks5u2rzxgaJpZM4ZHXIl> .

[Katharine]

I'm pretty sure none of this has been put through any sort of pass beyond "yes, this is technically capable of rendering information from artifacts". There has been slightly more effort on the build logs.

[ibzib]

re metadata viewer, I put in #10406. I wouldn't say it looks good now, but at least it's not spread out into different tables and cluttered with empty fields anymore.

[Katharine]

I did some work on the UI to prettify it in #10929 / #10932, which hopefully at least mostly resolves the broadest design complaints (@spiffxp):

[spiffxp]

Will also want to update links in go.k8s.io/triage (test-infra/triage)

[Katharine]

This happened.