-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins 2.32.3, warnings plugin 4.60
I have a pipeline job where the warnings are displayed only sometimes. When building a new commit, they are there. Rebuilding that commit shows the warnings, until it doesn't anymore. Rebuilding after that doesn't bring them back in the report (of course they are present in the log). If it should matter, it is with the Erlang parser.
- duplicates
-
JENKINS-32191 workflow plugin does not provide console to warnings plugin, sleep required
-
- Resolved
-
As you can see, builds 24 to 30 are for the same commit. #27 reports no warnings (not only the graph). The logs for each run are identical (except timestamps and such). The relevant lines are below the image, as well as the excerpt from the Jenkinsfile calling the reporter.
===> Compiling erlide_ide
_build/default/lib/erlide_ide/src/model/erlide_db.erl:24: Warning: type kind() is unused
_build/default/lib/erlide_ide/src/model/erlide_db.erl:100: Warning: function module_key/1 is unused
_build/default/lib/erlide_ide/src/model/erlide_db.erl:103: Warning: function module_props/2 is unused
step([$class: 'WarningsPublisher', canComputeNew: false, canResolveRelativePaths: true, canRunOnFailed: true,
consoleParsers: [[parserName: 'Erlang Compiler (erlc)'], [parserName: 'Maven']],
excludePattern: '', healthy: '', includePattern: '', messagesPattern: '', unHealthy: ''])