Skip to content

[JENKINS-68856] Remote API should use paths for affected files relative to specified source directory #3092

@jenkins-infra-bot

Description

@jenkins-infra-bot

When setting the sourceDirectory option to be a path relative to the workspace (due to a checkout to a subdirectory), the source files are still shown with a path relative to the workspace. I would expect them to have a path relative to the sourceDirectory given. This is relevant when sending the filenames to a code review system that expect them to be relative to the checkout directory.


Originally reported by nickb_carallon, imported from: Remote API should use paths for affected files relative to specified source directory
  • status: Open
  • priority: Minor
  • component(s): warnings-ng-plugin
  • label(s): hacktoberfest, help-wanted, newbie-friendly
  • resolution: Unresolved
  • votes: 0
  • watchers: 3
  • imported: 2025-12-09
Raw content of original issue

When setting the sourceDirectory option to be a path relative to the workspace (due to a checkout to a subdirectory), the source files are still shown with a path relative to the workspace. I would expect them to have a path relative to the sourceDirectory given. This is relevant when sending the filenames to a code review system that expect them to be relative to the checkout directory.

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions