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

Allow to configure the git blame command to suppress whitespace changes

      Sometimes the git blame command does not find the right person as there were whitespace changes (e.g. due to formatting) or code was moved. In this case it is possible to use "git blame -w -M" to suppress commits that only contain those changes and get better results

      I suggest to make the used git blame command configurable.

       

      There are two possible places:

      1. in the global configuration.
      2. in the warnings step itself.

      As the implementation in the global settings is much easier I guess it could be done there. The only reason not to have it there would be to have different settings for different parsers (e.g. if you have one parser in the job that would be sensitive to whitespace changes).

          [JENKINS-55719] Allow to configure the git blame command to suppress whitespace changes

          Till Steinbach created issue -
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]
          Labels New: help-wanted
          Ulli Hafner made changes -
          Component/s New: git-forensics-plugin [ 25321 ]
          Component/s Original: warnings-ng-plugin [ 24526 ]
          Ulli Hafner made changes -
          Labels Original: help-wanted New: help-wanted newbie-friendly
          Ulli Hafner made changes -
          Rank New: Ranked lower
          Ulli Hafner made changes -
          Labels Original: help-wanted newbie-friendly New: hacktoberfest help-wanted newbie-friendly

            Unassigned Unassigned
            tstein Till Steinbach
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: