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

Obtain parallel warnings results in pipeline

    Details

    • Similar Issues:
    • Released As:
      5.0.0-beta2

      Description

      I currently use the warnings plugin in a pipeline build by simply calling the build step. Doing this sets the build result to unstable, so I was checking that during the pipeline to determine whether some extra steps to run.

      Specifically, I have a parallel build, which builds on multiple different configurations in parallel, and I want to rename the log file for each build to "unstable" only if that configuration got warnings. However, the build result is global for the whole pipeline. How can I obtain the number of warnings or the "result" of the warnings step in such a way that each parallel invocation can get its own results? This allows me to rename my logged files so that users who look at the final results can quickly determine which configurations were faulty?

        Attachments

          Issue Links

            Activity

            Hide
            jekeller Jacob Keller added a comment -

            Note that this can't even be done currently with the currentBuild.rawBuild manually. Even if you manage to get the actions, there's no way to tell which WarningsResultAction actually contains the warnings you care about, since the ParserResult doesn't store which workspace files it scans.

            Show
            jekeller Jacob Keller added a comment - Note that this can't even be done currently with the currentBuild.rawBuild manually. Even if you manage to get the actions, there's no way to tell which WarningsResultAction actually contains the warnings you care about, since the ParserResult doesn't store which workspace files it scans.
            Hide
            jekeller Jacob Keller added a comment -

            Actually, I think all you need to do is create a step which takes a parser configuration and creatse a FileParser object, execute it, and return the ParserResult... That might not be too complicated.

            Show
            jekeller Jacob Keller added a comment - Actually, I think all you need to do is create a step which takes a parser configuration and creatse a FileParser object, execute it, and return the ParserResult... That might not be too complicated.
            Hide
            drulli Ulli Hafner added a comment -

            That is exactly what I mean. I think I will write down these ideas in a wiki page so that everybody can help to refine these requirements before I can start with an implementation...

            Show
            drulli Ulli Hafner added a comment - That is exactly what I mean. I think I will write down these ideas in a wiki page so that everybody can help to refine these requirements before I can start with an implementation...
            Hide
            drulli Ulli Hafner added a comment -

            I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page. Can you please read it carefully and comment or change it accordingly?

            Show
            drulli Ulli Hafner added a comment - I'm trying to consolidate the requirements for the static analysis suite in pipeline jobs in a wiki page . Can you please read it carefully and comment or change it accordingly?
            Hide
            drulli Ulli Hafner added a comment -

            Released in 5.0.0-beta2.

            Show
            drulli Ulli Hafner added a comment - Released in 5.0.0-beta2.

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                jekeller Jacob Keller
              • Votes:
                4 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: