Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
Description
Currently, all paths are resolved to an absolute path. It would rather make sense to store a relative path only in the issue and link to the base folder in a report.
Attachments
Issue Links
- blocks
-
JENKINS-60973 Use relative paths in remote API
-
- Resolved
-
- is blocking
-
JENKINS-58538 Support for relative paths in folder view
-
- Resolved
-
I think this is also needed in order to properly handle scans of parallel nodes. Different build nodes aren't guaranteed to have the same root folder, or if a single node is running multiple parallel blocks at once the workspace path contains @2, @3, etc... This results in the same warning getting counted either once if workspace paths match or multiple times if the workspace path does not match. We compile C++ for multiple targets in a single job, or to also run unit tests with coverage enabled, so parallel and the same compiler running on the same file is helpful and common. Storing only the relative path should mean that the same warning from different passes on the same file only gets counted once regardless of the number of times it was output.