You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding documentation each repo is checked out to a custom path $(Pipeline.Workspace)/s/RepoName if use multi-checkouts.
In scans result section filenames have wrong links with RepoName
so it causes the error I try to see the file in a repo:
The text was updated successfully, but these errors were encountered:
This is tricky. The viewer constructs those URLs from the "version control provenance" object it receives, which (if it doesn't exist) this extension defaults to the repository that the build is linked to, not necessarily the repo that the results are from. So that seems to point to two things that need doing:
This extension needs to figure out if multi-checkout is happening (somewhat difficult).
The viewer needs to have an option to strip portions of the relative URI.
Regarding documentation each repo is checked out to a custom path $(Pipeline.Workspace)/s/RepoName if use multi-checkouts.
In scans result section filenames have wrong links with RepoName
so it causes the error I try to see the file in a repo:
The text was updated successfully, but these errors were encountered: