Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Won't Fix
-
Component/s: warnings-plugin
-
Labels:
-
Environment:workflow-plugin 1.12
warnings plugin 4.51
jenkins 1.641
-
Similar Issues:
Description
I came up with the following workflow script brooken.groovy, which
compiles a file with clang, and then invokes the warnings plugin.
In the console log, there are warnings, but the warnings plugin detects zero warnings.
I modified the script slightly (fixed.groovy) by inserting a sleep statement before calling the warnings plugin. I re-ran the script and the warnings plugin detected the warnings.
It looks like the workflow-plugin is not providing the console to the warnings plugin when it needs it? Maybe a flush is missing?
Attachments
Issue Links
- is duplicated by
-
JENKINS-42642 Warnings reported intermittently
-
- Resolved
-
- relates to
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
-
- Resolved
-
-
JENKINS-55215 Log from cmake/ctest steps isn't fully captured on OsX
-
- Open
-
Not sure how it could be working in CI. That there are bad deps is backed up by:
Possibly the issue is something to do with the timestamped snapshot dependencies (analysis-model-api.version + analysis-model.version) malfunctioning, and the Maven build pulling in more or less random versions of stuff. I would advise you to switch to JEP-305. It is generally not hard to do and you can bypass a lot of weird issues.