At the moment warnings-ng doesn't support the git-feature submodule.

      In the log the plugin promts the following error

      Git blame errors:
      no blame results for request <Module/UtilityLib/Source/UtilMath.c - [534]>.
      

      Egit returns null for the request.

       

          [JENKINS-56215] git submodule support

          Tim Schlüter created issue -

          Ulli Hafner added a comment -

          Which git plugin and git client plugin versions are you using?

          Can you please check if it is possible to obtain a git blame from your Jenkins workspace using the git command line? I'm not sure if this is a problem in the jgit library or if such a workspace can't provide blames at all using the git command line.

          Ulli Hafner added a comment - Which git plugin and git client plugin versions are you using? Can you please check if it is possible to obtain a git blame from your Jenkins workspace using the git command line? I'm not sure if this is a problem in the jgit library or if such a workspace can't provide blames at all using the git command line.
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]
          Labels Original: git plugin New: help-wanted
          Tim Schlüter made changes -
          Environment New: git plugin - 3.9.3
          git client plugin - 2.7.6

          Tim Schlüter added a comment -

           

          $ git blame Module/UtilityLib/Source/UtilMath.c                      
          fatal: no such path 'Module/UtilityLib/Source/UtilMath.c' in HEAD               
          $ ls Module/UtilityLib/Source/UtilMath.c                               
          Module/UtilityLib/Source/UtilMath.c  
          

           

          Tim Schlüter added a comment -   $ git blame Module/UtilityLib/Source/UtilMath.c fatal: no such path 'Module/UtilityLib/Source/UtilMath.c' in HEAD $ ls Module/UtilityLib/Source/UtilMath.c Module/UtilityLib/Source/UtilMath.c  

          Ulli Hafner added a comment -

          I see. If this is not possible in git then it is not possible in my plugin. I don't see what I can do here

          Ulli Hafner added a comment - I see. If this is not possible in git then it is not possible in my plugin. I don't see what I can do here

          Tim Schlüter added a comment -

          Changing the directory would work

          $ cd Module/UtilityLib/                                                                                                                                      
          $ git blame Source/UtilMath.c                                                                                                                        
          0372016e (userx 2015-08-24 15:43:28 +0200   1) /**@file**********************************************************************                                                                                                               
          76b7d993 (usery 2015-10-13 12:05:32 +0200   2)                                                                                                              
          889358ba (userx 2015-08-24 15:48:29 +0200   3)   Copyright(c) Alle Rechte sowie jede Verfuegungsbefugnis,                                                                                                                                   
          ...

           

          Tim Schlüter added a comment - Changing the directory would work $ cd Module/UtilityLib/ $ git blame Source/UtilMath.c 0372016e (userx 2015-08-24 15:43:28 +0200 1) /**@file********************************************************************** 76b7d993 (usery 2015-10-13 12:05:32 +0200 2) 889358ba (userx 2015-08-24 15:48:29 +0200 3) Copyright(c) Alle Rechte sowie jede Verfuegungsbefugnis, ...  

          Ulli Hafner added a comment -

          Then it should be feasible somehow. GitBlamer needs to be adapted to detect the advanced feature Submodules from the git scm step and then somehow changes the processing of the files.

          Ulli Hafner added a comment - Then it should be feasible somehow. GitBlamer needs to be adapted to detect the advanced feature Submodules from the git scm step and then somehow changes the processing of the files.

          Simon Wright added a comment -

          Simon Wright added a comment - Workaround: disable blaming, see  https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#source-code-blames-for-git-projects
          Ulli Hafner made changes -
          Link New: This issue is duplicated by JENKINS-62119 [ JENKINS-62119 ]

            Unassigned Unassigned
            timsch Tim Schlüter
            Votes:
            5 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: