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

warnings-plugin aborts if unable to git-blame.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-plugin
    • None

      The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

      In my source project some .c-files are generated, obviously these will not be in git.

      There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

       

      ...
End of build script
[WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
<Git Blamer> Using GitBlamer to create author and commit information for all warnings.
<Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
> git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^{commit} # timeout=10
<Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
<Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
...
<Git Blamer> No blame results for request <build/fader21/flasm/generated/asm.lex.c - [37726]>.
<Git Blamer> No blame results for request <build/fader23/flasm/generated/asm.lex.c - [69737]>.
Build step 'Console output (build log) parsing' changed build result to ABORTED
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: ABORTED

          [JENKINS-49508] warnings-plugin aborts if unable to git-blame.

          Erik Jonsson created issue -
          Ulli Hafner made changes -
          Description Original: The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

          In my source project some .c-files are generated, obviously these will not be in git.

          There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

           

          <Git Blamer> Using GitBlamer to create author and commit information for all warnings.
          <Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
          > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^\{commit} # timeout=10
          <Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
          <Git Blamer> No blame results for request <build/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/sleipnir/flasm/generated/asm.lex.c - [16174]>.           		New: The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

          In my source project some .c-files are generated, obviously these will not be in git.

          There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

           {noformat}
          <Git Blamer> Using GitBlamer to create author and commit information for all warnings.
          <Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
          > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^\{commit} # timeout=10
          <Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
          <Git Blamer> No blame results for request <build/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/sleipnir/flasm/generated/asm.lex.c - [16174]>.
           {noformat}

          Ulli Hafner added a comment -

          Do you also have that part of the log that shows that the build is aborted? The log currently shows only some warnings.

          Ulli Hafner added a comment - Do you also have that part of the log that shows that the build is aborted? The log currently shows only some warnings.
          Erik Jonsson made changes -
          Description Original: The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

          In my source project some .c-files are generated, obviously these will not be in git.

          There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

           {noformat}
          <Git Blamer> Using GitBlamer to create author and commit information for all warnings.
          <Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
          > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^\{commit} # timeout=10
          <Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
          <Git Blamer> No blame results for request <build/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/sleipnir/flasm/generated/asm.lex.c - [16174]>.
           {noformat}
          		 New: The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

          In my source project some .c-files are generated, obviously these will not be in git.

          There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

           
          {noformat}
          ...
          End of build script
          [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
          <Git Blamer> Using GitBlamer to create author and commit information for all warnings.
          <Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
          > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^{commit} # timeout=10
          <Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
          <Git Blamer> No blame results for request <build/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/sleipnir/flasm/generated/asm.lex.c - [16174]>.
          <Git Blamer> No blame results for request <build/thor/flasm/generated/asm.lex.c - [10090]>.
          ...
          Build step 'Console output (build log) parsing' changed build result to ABORTED
          [BFA] Scanning build for known causes...
          [BFA] No failure causes found
          [BFA] Done. 0s
          Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Finished: ABORTED
          {noformat}

          Erik Jonsson added a comment -

          Yes, it's now updated.

          Erik Jonsson added a comment - Yes, it's now updated.
          Erik Jonsson made changes -
          Description Original: The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

          In my source project some .c-files are generated, obviously these will not be in git.

          There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

           
          {noformat}
          ...
          End of build script
          [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
          <Git Blamer> Using GitBlamer to create author and commit information for all warnings.
          <Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
          > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^{commit} # timeout=10
          <Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
          <Git Blamer> No blame results for request <build/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/sleipnir/flasm/generated/asm.lex.c - [16174]>.
          <Git Blamer> No blame results for request <build/thor/flasm/generated/asm.lex.c - [10090]>.
          ...
          Build step 'Console output (build log) parsing' changed build result to ABORTED
          [BFA] Scanning build for known causes...
          [BFA] No failure causes found
          [BFA] Done. 0s
          Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Finished: ABORTED
          {noformat}           		New: The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.

          In my source project some .c-files are generated, obviously these will not be in git.

          There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings.

           
          {noformat}
          ...
          End of build script
          [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
          <Git Blamer> Using GitBlamer to create author and commit information for all warnings.
          <Git Blamer> GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm
          > git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^{commit} # timeout=10
          <Git Blamer> No blame results for request <build_decode_32/thor/simgen/generated/decoder.c - [132, 2126]>.
          <Git Blamer> No blame results for request <build/fader22/flasm/generated/asm.lex.c - [64410]>.
          ...
          <Git Blamer> No blame results for request <build/fader21/flasm/generated/asm.lex.c - [37726]>.
          <Git Blamer> No blame results for request <build/fader23/flasm/generated/asm.lex.c - [69737]>.
          Build step 'Console output (build log) parsing' changed build result to ABORTED
          [BFA] Scanning build for known causes...
          [BFA] No failure causes found
          [BFA] Done. 0s
          Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Finished: ABORTED
          {noformat}

          Ulli Hafner added a comment -

          The text 

          Build step 'Console output (build log) parsing' changed build result to ABORTED

          seems to be from a different plugin, are you using the console parser plugin? Is there a rule defined to abort the build on a warning message?

          Ulli Hafner added a comment - The text Build step 'Console output (build log) parsing' changed build result to ABORTED seems to be from a different plugin, are you using the console parser plugin? Is there a rule defined to abort the build on a warning message?

          Erik Jonsson added a comment -

          Yes, that must have been the problem.

          I got it working now. Sorry about this missunderstandig.

          Erik Jonsson added a comment - Yes, that must have been the problem. I got it working now. Sorry about this missunderstandig.
          Erik Jonsson made changes -
          Assignee Original: Ulli Hafner [ drulli ] New: Erik Jonsson [ nesqi ]

          Erik Jonsson added a comment -

          Acuall issue was with a different plugin.

          Erik Jonsson added a comment - Acuall issue was with a different plugin.
          Erik Jonsson made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            nesqi Erik Jonsson
            nesqi Erik Jonsson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: