Console logged URI's in internal builds are hard to use

Migrated from https://github.com/dotnet/core-eng/issues/15366

@ChadNedzlek wrote:

Split from https://github.com/dotnet/core-eng/issues/15335

We found some usability issues while working through problems in the https://dev.azure.com/dnceng/internal/_git/dotnet-aspnetcore/pullrequest/20208 pull request. (Background note: Tests are enabled in internal verification builds of PRs like this.)

Taking https://dev.azure.com/dnceng/internal/_build/results?buildId=1551770&view=results as an example:

1. The Artifacts tab for any failed work item in for example Pipelines - Run 20220113.15 (azure.com) is empty. I’m not sure if the problem is permissions (this is an internal PR after all), core dumps flooding the system, or something else.
2. Console logs don’t exist at all when the Python code fails before opening a console. This makes the failure links in the build step 404.
3. Separately and someone less annoyingly (since pasting a token is required anyhow), navigating from the work item list provided in the build step logs to a specific details URI means adding &access_token={token} instead of changing {Get to your token.

[dougbu]

@dougbu, you good with us removing these URIs and replacing it with that direction?

Yup, this works for me. Less links, less confusion 😄

[ChadNedzlek]

I don’t like the console logged URI’s at all. They are a lame way to get at what the artfiacts tab is much better at showing you. Honestly the error should just be “your tests failed, go to the artifacts tab to see details”