Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62119

Warnings Next Generation support Git Submodules

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • Jenkins ver. 2.204.4
      Warnings Next Generation 7.2.2
      Git-Forensics 0.6.0

      Given that we have the following repo structure:
      <General Build Repo>

      _/<submoduleProject>

      And we call the build in <general build repo> so the warnings paths are relative to <general build repo>, git blame doesn't work because the blame information is in <submoduleProject>.

      A possible solution would be to do an aequivalent to the following:
      Instead of: "git blame <submoduleProject>/path/to/file"
      do: "cd <submoduleProject>/path/to ; git blame file"

      That way the correct would always be selected to retrieve the blame info (a minor performance hit is possible).

            Unassigned Unassigned
            snapstromegon Raphael Höser
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: