-
Bug
-
Resolution: Fixed
-
Major
-
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.
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?
Yes, that must have been the problem.
I got it working now. Sorry about this missunderstandig.
Do you also have that part of the log that shows that the build is aborted? The log currently shows only some warnings.