Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Not A Defect
-
Tried both with:
- a windows master, and a linux slave. Jenkins 1.440 Warnings 3.24
- a linux box (different from the above) acting both as master and slave, Jenkins 1.440, Warnings 3.24
Description
I create my own parser. If I use the Warning parsing on the master it works as expected. If I make the parsing on the slave it always reports 0 warnings
Attachments
Issue Links
- is related to
-
JENKINS-12280 Warnings plugin does strange things with a custom parser
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Affects Version/s | current [ 10162 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Link |
This issue is related to |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Attachment | issue11926.txt [ 21529 ] |
Resolution | Not A Defect [ 7 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Workflow | JNJira [ 142169 ] | JNJira + In-Review [ 190013 ] |
How did you create the parser? Using the UI or by implementing the extension point?