Add /log/$log URL |
||||||||
Issue descriptionWith buildbot one can take waterfall/builder/build number/step and build a path to the logs. To do so with logdog requires parsing the annotations and searching for all streams which match the step name. Make a helper which does the annotation parsing and lookup and redirects to the correct logdog viewer page.
,
Mar 10 2017
:D
,
Mar 20 2017
I'm not quite sure I follow. If we have a build, we can construct the path to it (eg "chromeos/cyan-chrome-pfq/912"), how do we used the /logdog/build and specify the step name (eg "VMTest (attempt 1)") with a generated URL that gets us to the logs, similar to how we could with buildbot?
,
Mar 20 2017
,
Mar 20 2017
I've misinterpreted your request.
,
Mar 20 2017
,
Mar 20 2017
I don't think this is a LogDog component bug, since all of the data is available. Milo will need to: 1) Load BuildInfo for the build in question. 2) Look up the requested step against the step protobuf. 3) Redirect to the log viewer. This is all Milo code here.
,
Apr 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 29 2018
Ryan, can you help triage this? Is this already possible to do (I think not, but would love to be proven wrong)? Is this on our (Milo/LogDog) plate?
,
May 29 2018
I believe this is the /log/$log url schema as proposed in https://docs.google.com/document/d/1wnUOrusBq3-DU3NQ8bDIH6Tn6QQzS-C_VnopWHq5np8/edit#heading=h.w32d72usmw4o Is that what the OP is asking for? Milo does not currently do this, but it could. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by no...@chromium.org
, Mar 10 2017Status: Fixed (was: Untriaged)