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

Warnings plugin does not work on a slave

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: warnings-plugin
    • Environment:
      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
    • Similar Issues:

      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

            Activity

            Hide
            drulli Ulli Hafner added a comment - - edited

            Massimo, I think that the problem must be somewhere else. Maybe the output file is different. Would it be possible to attach the output as a file? Or conversely, can you check if the attached file issue11926.txt will be parsed by your parser if you copy it to the slave (or master).

            Show
            drulli Ulli Hafner added a comment - - edited Massimo, I think that the problem must be somewhere else. Maybe the output file is different. Would it be possible to attach the output as a file? Or conversely, can you check if the attached file issue11926.txt will be parsed by your parser if you copy it to the slave (or master).
            Hide
            maxrossello Massimo Rossello added a comment -

            Ok, I will try to parse your attached file as soon as possible.
            Thanks

            Show
            maxrossello Massimo Rossello added a comment - Ok, I will try to parse your attached file as soon as possible. Thanks
            Hide
            torbent torbent added a comment -

            Wild guesses; maybe helpful, maybe confusing:

            • Permission problem? Is the log file readable on the slave by the user that runs the Jenkins service?
            • In our setup, the workspaces are on network drives and reachable from both master and slave (although not at identical paths). Could it be that both server and slave need access to the workspace for dynamic warnings parsing to work?
            • Or perhaps the expression just doesn't match? For example I'd guess that $5 is wrong (should probably be (.*)). Does the dynamic parser expect to be able to match a whole line?
            • Did you happen to forget restarting Jenkins after installing Warnings 3.27?

            Hope this helps. My very similar JENKINS-12280 issue seems to be solved by version 3.27 (a little extra test is still pending).

            Show
            torbent torbent added a comment - Wild guesses; maybe helpful, maybe confusing: Permission problem? Is the log file readable on the slave by the user that runs the Jenkins service? In our setup, the workspaces are on network drives and reachable from both master and slave (although not at identical paths). Could it be that both server and slave need access to the workspace for dynamic warnings parsing to work? Or perhaps the expression just doesn't match? For example I'd guess that $5 is wrong (should probably be (.*)). Does the dynamic parser expect to be able to match a whole line? Did you happen to forget restarting Jenkins after installing Warnings 3.27? Hope this helps. My very similar JENKINS-12280 issue seems to be solved by version 3.27 (a little extra test is still pending).
            Hide
            maxrossello Massimo Rossello added a comment -

            Solved.

            I did not notice that some colleague of mine slightly changed the format of the output.

            Thanks to everybody!
            Massimo

            Show
            maxrossello Massimo Rossello added a comment - Solved. I did not notice that some colleague of mine slightly changed the format of the output. Thanks to everybody! Massimo
            Hide
            maxrossello Massimo Rossello added a comment -

            Issue reopening was due to an error in usage

            Show
            maxrossello Massimo Rossello added a comment - Issue reopening was due to an error in usage

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                maxrossello Massimo Rossello
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: